AnQi CMS is an efficient enterprise-level content management system, and its powerful multi-site management function undoubtedly brings convenience to many operators.It allows us to easily manage multiple independent content platforms on a unified backend.However, many users who are new to the multi-site mode often have a question: if we need to stop or maintain one of the sites in an AnQiCMS instance, will it affect the other sites that are running normally?Today, let's delve into this issue and share some practical operation suggestions.
Does stopping one site affect the operation of other sites in the multi-site mode of AnQiCMS?
The answer is:In most cases, stopping one site will not affect the normal operation of other sites.AnQiCMS was designed with full consideration of the independence and isolation between multiple sites, aiming to provide a stable and non-interfering operating environment.Its core mechanism ensures that each site has its own independent running environment and data storage, thereby avoiding the risk of 'all rise or fall together'.
This independence is mainly reflected in the following aspects:
Firstly,The physical isolation of data storage is the core guarantee.According to AnQiCMS's document instructions, in multi-site mode, whenever you add a new site through the "Multi-site Management" feature in the backend, the system will allocate an independent database for it.This means that all the content, users, configuration, and other data for site A are stored in its own database, completely separate from the data of site B.Even if the data at site A has a problem and needs to be restored, or is disabled for some reason, the operation will only affect its own data and will not affect the databases of other sites.This physical-level data isolation is the cornerstone of stable multi-site operation.
Secondly,The independence of files and cache mechanisms provides runtime protection. AnQiCMS creates a separate site root directory for each site (for example/app/dev_anqicms.com
Moreover,The efficient concurrency features of Go language lay a solid foundation for independent operation
Through such architecture design, AnQiCMS achieves a high degree of isolation between sites, so that operations on a single site (such as disabling, deleting, or performing data maintenance in the background) are limited to that site itself and will not affect other sites running under the AnQiCMS instance.
When might it be affected? Special scenarios and operational suggestions
Although AnQiCMS is committed to achieving independence among sites in terms of architecture, it may still be the case that a slight change can lead to a domino effect, or it requires our extra attention:
- The shutdown or crash of the AnQiCMS application process: