English CMS (EnglishCMS) provides an efficient and flexible solution for operators who have multiple brands, sub-sites, or content branches with its powerful multi-site management function.It allows you to easily create, manage, and display multiple independently operated websites under the same core system, greatly enhancing the efficiency of content operation.

Understanding the multi-site architecture of AnQiCMS

The elegance of AnQiCMS lies in the fact that you only need to install one core system to easily create and manage multiple independent websites without needing to redeploy programs for each site. This architecture brings significant advantages:

Firstly, it has implementedUnified management. You can overview the operation status of all sites through a main background entry and delve into the management interface of specific sites when needed. Secondly, this modereduces duplicate work.For example, system upgrades, security maintenance, and other operations only need to be executed on the core system to benefit all sub-sites. Again, each site can havean independent content system and management interfaceEnsure the focus of content operation and data isolation, while also supportingResource integration and data sharing possibilities, providing a foundation for more complex operation strategies.

Multi-site deployment and configuration: from server to CMS backend

To allow multiple sites to coexist and operate independently in AnQiCMS, typically, two core configurations are required: the domain and reverse proxy settings on the server side, as well as the site registration in the AnQiCMS backend.

1. English server-level basic configuration

No matter whether you deploy through Docker on a management panel like 1Panel, aaPanel, or directly configure Nginx or Apache on the server, the core idea is to use reverse proxy technology to direct different domain names to the same running port of your AnQiCMS (usually the default is)8001).

For example, if you have two domain namessiteA.comandsiteB.comYou need to set up reverse proxy rules for these two domain names in the Web server configuration on the server (such as Nginx), both pointing to the running port of AnQiCMS. The Nginx configuration is roughly as follows: 

# siteA.com 的配置
server {
    listen 80;
    server_name siteA.com www.siteA.com;

    location / {
        proxy_pass http://127.0.0.1:8001; # 指向AnQiCMS的端口
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
}

# siteB.com 的配置
server {
    listen 80;
    server_name siteB.com www.siteB.com;

    location / {
        proxy_pass http://127.0.0.1:8001; # 同样指向AnQiCMS的端口
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
}

Configuration completed, please make sure that your domain name is correctly resolved to the server IP.

2. AnQiCMS backend site registration

After completing the server configuration, the next step is to register the new site on AnQiCMS backend. You need to log in to the backend of the initially installed AnQiCMS main site (usually主域名/system/），In the left menu, find and enter the "Multi-site Management" function.

Here, click "Add New Site", and the system will require you to fill in the details of the new site:

  • Site Name:Used to distinguish between different sites, and can be named according to actual circumstances.
  • Site root directory:This is a very critical setting, used to independently store new site cache, logs, uploaded files, and other data to ensure data isolation. It must be/app/(If it is a Docker environment) or/www/wwwroot/starts with, and add a directory name based on the domain name that is not repeated, for example/app/site_a_comor/www/wwwroot/site_a_com.
  • Website address:the complete URL of the new site, for examplehttp://siteA.com.
  • Administrator account password:Set an independent admin account and password for the new site.
  • Database name:Similarly, you need to specify a unique database name for the new site to avoid confusion with existing site data, for examplesite_a_com_db.
  • Database information reuse:If your AnQiCMS is installed using Docker and you have full database management permissions, you can usually choose 'Reuse default database account information' to skip the step of re-entering database credentials.
  • Select the template you want to use:For new