# Common Issues with Community Edition Deployment
# 1. What is the Community Edition?
The Community Edition is our free private deployment service provided for developers. Developers can follow the instructions to complete the private deployment of FinClip core services.
There are no significant functional differences in the Community Edition. The main distinctions are that the Community Edition allows the creation of only 2 Mini-Programs, adding 1 collaborative application, and does not include data analytics services. In the official deployment version of FinClip, there are no such limitations.
# 2. How to Deploy the Community Edition?
The Community Edition can be deployed using either cloud servers or local servers. For detailed download and deployment instructions, please refer to:
- Introduction - Quick Deployment - One-Click Terminal Deployment
- Introduction - Quick Deployment - Windows Deployment Guide
- Introduction - Quick Deployment - macOS Deployment Guide
- Introduction - Quick Deployment - Linux Deployment Guide
# 3. Which Steps Require Internet Access When Deploying the Community Edition in an Intranet Environment?
In one-click deployment, there are three steps that require internet access. Please ensure that the network control settings for the server used for "deployment services" are adjusted as follows:
# 3.1 Download Docker
- Type: Outbound server request (mandatory)
- Allowed addresses: [Outbound] 0.0.0.0/0
Note
Downloading Docker requires access to our CDN download server and package management tools like yum, apt-get, etc., from the system's repo. Since this scenario does not have a fixed IP address, it is impossible to create a whitelist based on IP addresses. Therefore, all outbound requests to 0.0.0.0/0 must be allowed.
# 3.2 Download Deployment Kit
- Type: Outbound server request (mandatory)
- Allowed addresses: [Outbound] 0.0.0.0/0
Note
The "deployment files" and "image packages" used for deployment services will request Tencent Cloud's object storage service. Tencent Cloud may adjust the IP addresses corresponding to the "object storage service" based on its own circumstances. Hence, it is also impossible to establish an IP whitelist, and all outbound requests to 0.0.0.0/0 must be allowed.
# 3.3 Provide Services
- Type: Outbound server request (mandatory), Inbound server request (optional)
- Allowed addresses: [Outbound] 123.207.110.121, [Inbound] {relevant IP}:{port used during deployment}
Note
After the service deployment is completed, if it is a local deployment or server deployment that can be accessed via the intranet, there is no need to open public inbound access. If the server is deployed but cannot be accessed via the intranet (common in leased cloud server deployments without a VPN connection), then public inbound access must be enabled for this cloud server (which may include security groups). The source IP depends on the situation, while the destination IP is the public or private IP of the deployment server; the port is the one specified in the script during the deployment process.
In addition to public inbound access, outbound requests must also be allowed, but the address can be restricted to 123.207.110.121 or build.finogeeks.club. When compiling Mini-Programs online and using related functions, requests to this address are required.