Community Edition Deployment FAQ
1. What is Community Edition?
Community Edition is our free version of the privatization service for developers, who can follow the guidelines to complete the privatization deployment of PhizClip core services.
The main difference is that the Community Edition can only create 5 mini-apps and add 1 partner app, and does not include statistics service. In the official deployment of PhizClip, there are no limitations on functionality.
2. How do I deploy the Community Edition?
You can use either cloud server or local server to deploy the community edition, for details and instructions, please see
3. When deploying Community Edition in an intranet environment, which parts need to be connected to the external network
The following three parts of the one-click deployment must use the extranet, please make sure to adjust the network control for the server used to "deploy the service" with the following conditions.
3.1 Downloading Docker
- Type: server outbound request (required)
- Release address: [outbound] 0.0.0.0/0
TIP
Docker download requires access to our CDN download server and repo of package management tools such as yum, apt-get, etc. There is no fixed IP address for this scenario, so it is not possible to create a whitelist list for IPs, so you need to release all addresses of 0.0.0.0/0 for public network outbound.
3.2 Downloading the deployment kit
- Type: server outbound request (required)
- Release address: [outbound] 0.0.0.0/0
TIP
The "deployment files" and "image packages" used for deployment services will request Tencent Cloud's object storage service. Tencent Cloud may adjust the IP address corresponding to the "Object Storage Service" due to its own situation, so it agrees that it cannot create a whitelist list for IPs, and needs to release all addresses of 0.0.0.0/0 for public network outbound.
3.3 Provisioning services
- Type: server outbound request (required), server inbound request (optional)
- Release address: [outbound] 123.207.110.121, [inbound] {relevant IP}:
TIP
After the service is deployed, if the service is deployed locally, or if the server is deployed but can be accessed on the intranet, there is no need to open the public inbound. If the server is deployed but intranet access is not available (common for leased cloud server deployments where VPN connectivity is not established), a public inbound request release is required for this cloud server (possibly including security groups). The source IP of the release depends on the situation, while the destination IP is the public and intranet IP of the deployed server; the port is the port filled in the script during the deployment session.
In addition to public inbound, you also need to release public outbound requests, but only 123.207.110.121 or build.Phiz.club are allowed to be released, and you need to request this address when compiling applets online.