As a senior security CMS website operator, I know full well the core role of the content management system in today's digital marketing.Especially when facing the needs of multi-site operations, the powerful functions and flexible configuration provided by AnQiCMS are undoubtedly our powerful assistant.How to properly configure the root directory of a new site to achieve data isolation is a key link to ensure the efficient and secure operation of multiple sites.

The value of AnQiCMS multi-site management and the necessity of data isolation

One of the core advantages of AnQiCMS is its excellent multi-site management capabilities.This allows us to efficiently manage multiple brands, different business lines, or multilingual content sites through a unified backend system.This centralized management model greatly reduces repetitive work, improves operational efficiency, and facilitates the integration and sharing of cross-site content.

However, while enjoying the convenience brought by multi-site management, we must also pay high attention to the issue of data isolation.Imagine if all the cache, uploaded files, logs, and other data from all sites were mixed together. Once an issue occurs with a site, or when data migration and backup are needed, management becomes extremely complex, and it may even trigger a chain reaction, affecting the normal operation of other sites.Therefore, configuring an independent root directory for each logical site, just as allocating independent storage space for each tenant, is the foundation for ensuring data security, maintaining system stability, and simplifying the operation and maintenance work in the later stage.It can effectively prevent data pollution and conflicts, and ensure a high degree of independence between sites.

Practical methods for configuring the root directory of a new site to achieve data isolation

To implement data isolation in the multi-site deployment of AnQiCMS, the core lies in the precise configuration of the "site root directory" and the "database name".The design concept of AnQiCMS is that a single core application instance can serve multiple logical sites and identify and load the corresponding site configuration through visiting domain names.

Firstly, when you need to add a new site under the same AnQiCMS instance, the first step is to log in to the AnQiCMS backend management interface of your main site.Find and click the "Multi-site Management

In the form of adding a new site, there are several key fields that we need to pay special attention to, as they are directly related to the implementation of data isolation:

Setting the root directory of the site

The root directory of the site is a dedicated file storage space exclusive to each logical site.This directory is used to store the uploaded images, attachments, cache files, logs, and possibly independent template files for this site.To ensure complete data isolation and avoid naming conflicts, we must set a unique and standardized directory name for each new site.

For AnQiCMS instances deployed using Docker, the recommended naming convention for the site root directory is usually/app/Start with, followed by a name converted from the site domain. For example, if your new site domain isdev.anqicms.com, then the suggested site root directory can be/app/dev_anqicms_comHere,_Replaced in the domain name with.，in order to comply with the naming conventions of the file system path. If you are deploying on a traditional Linux server through Baota panel or other methods, the root directory of the site can be set to/www/wwwroot/您的域名in the form of, for example/www/wwwroot/study.ykbh168.com.

No matter which deployment environment, the most important thing is to ensure that this directory name is unique throughout the AnQiCMS application file system and explicitly indicates which site the directory is serving.This will ensure that each site's non-database data (such as uploaded resources, cache, etc.) has its own independent storage path.

The independent configuration of the database name

The configuration of "database name" complements the root directory of the site.Each new site should have its own database, which is the most direct and thorough way to achieve data isolation for site content.dev_anqicms_com.

By using an independent database, we can ensure:

  • A site's articles, products, categories, users, and other core data will not be confused with data from another site.
  • When performing data backup, recovery, or migration, operations can be performed on specific sites without affecting other sites.
  • System updates or troubleshooting make it easier to locate the problem scope and reduce risks.

Under the Docker deployment scenario of AnQiCMS, it is usually possible to 'Reuse default database account information', because the AnQiCMS instance inside the Docker container usually has full database management permissions for the associated MySQL container.If you have special requirements or deploy the database externally, you need to fill in the corresponding database connection information according to the actual situation.

Reverse proxy settings of the front-end web server

Although the AnQiCMS core application may only run on a specific internal port (such as 8001), visitors access your various sites through different domain names.This requires the front-end web server (such as Nginx or Apache) to play its reverse proxy role.

You need to configure a reverse proxy rule for each new site domain on the Web server, forwarding all traffic to the address and port where the AnQiCMS core application is running (for examplehttp://127.0.0.1:8001）。When the AnQiCMS application receives these requests, it will intelligently identify which logical site's request it is based on the domain name in the request, and automatically load the independent site root directory and database configured for that site in the background.siteA.comwill seesiteAand use its independent data, while accessingsiteB.comwill seesiteBand use its independent data, all of which are processed by the same AnQiCMS instance.

Summary: High-efficiency and secure operation practices

Configure a separate site root directory and database for AnQiCMS multi-site deployment through the above steps, and we can build an efficient and secure content management ecosystem.This configuration mode not only optimizes resource management and improves system stability, but more importantly, it provides solid protection for the data of each site, ensuring their respective independence and integrity.As a website operator, adopting this practice is the key to achieving long-term, healthy, and scalable operations.

Common Questions (FAQ)

1. Why does each site need an independent 'site root directory'? What is the difference from database isolation?

Each site's independent "site root directory" is mainly used to store non-database data, such as: user-uploaded images, attachment files, system-generated cache files, log files, and possibly existing independent template files, etc.Its role is to ensure that these file-level data do not get confused or conflicted with each other, thus achieving data isolation at the file level.While database isolation refers to allocating an independent database for each site, which is used to store all structured data of the site, such as article content, category information, user data, etc.Both are different dimensions of data isolation, jointly forming the complete data security guarantee for multi-site deployment.

2. Does the multi-site deployment of AnQiCMS mean that a set of AnQiCMS program needs to be installed for each site?

Not required.AnQiCMS's multi-site function design is intended to manage multiple independent logical sites through a single AnQiCMS application instance.This means that you only need to install one set of AnQiCMS program, and then add and configure a new logical site through its "Multi-site Management" feature.Each logical site will have its own domain name, its own site root directory, and its own database, but they share the same AnQiCMS core application.This architecture greatly simplifies deployment and maintenance work.

3. If all my sites use the same template, do I still need an independent site root directory?

Even if all sites use the same template, it is strongly recommended to configure an independent site root directory for each site.Although template files may be shared, each site will still generate its own cache files, uploaded images and attachments (unless you have configured a shared bucket or CDN), as well as independent logs, etc.The independent site root directory can effectively isolate these non-template files data, prevent data confusion, and facilitate the operation of independently updating templates or performing data maintenance for a site in the future without affecting other sites.