As an experienced CMS operation person in the security field, I am well aware of the importance of system upgrades for the stable operation of the website, especially when managing multiple sites, any change may cause a chain reaction.The AnQi CMS has been upgraded from version 2.x to 3.x, the core of which lies in the innovation of underlying deployment and multi-site management mode, which will have a profound impact on your existing multiple sites, but on the whole, it is moving towards a more efficient and stable direction.
The characteristics of the multi-site management mode of AnQiCMS 2.x
In the Anqi CMS 2.x era, although the system had already possessed the ability to manage multiple sites, its implementation method was relatively traditional.If you run multiple Anqicms sites on the same server, you usually need to copy a set of independent Anqicms code for each site and run it separately on each oneconfig.jsonConfigure different ports in the file. In addition, each site may also require independent startup scripts and scheduled tasks to maintain its running status, such as starting and stopping.
The advantages of this model are that the sites are highly independent of each other, with no interference.However, its disadvantages are also very obvious: the deployment process is relatively complex, and each new site launch means repeated configuration and file operations;Resource usage may be high because each site runs an independent security CMS process;At the same time, the document also mentions that troubleshooting is more difficult for the 2.x version when encountering program problems, and it does not support restarting the service directly in the background, which brings inconvenience to daily maintenance.For users accustomed to managing through tools like Baota Panel, these manual configuration steps undoubtedly increase the cost of learning and operation.
Transformation of the deployment philosophy of AnQi CMS 3.x and multi-site integration
The AnqiCMS 3.x version introduces a completely new deployment philosophy, especially major optimizations in multi-site management.The new version no longer recommends running independent security CMS code and processes for each site.On the contrary, the design goal of version 3.x isManage all sites through a unified AnQi CMS executable.
This means that whether you deploy through Docker (for example, using the Docker app store of 1Panel or Baota panel), or deploy directly via the server command line, you will have a core security CMS service.This service is through its built-in multi-site management feature, which can unify scheduling and response to requests from different domain names, and map them to the corresponding site configuration and data.This single-process multi-site management mode significantly simplifies deployment and maintenance work, improving the overall operational efficiency and stability of the system.
Key steps and impacts during the upgrade process
Upgrading from AnQi CMS 2.x to 3.x is an integration and optimization process for users with multiple sites.The upgrade path is clear, detailed instructions are provided in the documentation:
First, you need to select an existing 2.x site as the 'default site' for upgrade.Log in to its backend and update it to the latest version through the system upgrade feature.After the upgrade is complete, you need to stop all 2.x version scheduled tasks and related processes.
The next critical step is to reconfigure the upgraded default site according to the deployment method of AnQi CMS 3.x (if you are using Baota panel, this will be simplified to "Add Go project").At configuration time, it points to the executable file and port of the original default site's security CMS, so that the system can identify and take over the existing data when it starts up without needing to reinitialize.
For your existing other multiple 2.x sites, the upgrade process is also similar.First, it is necessary to stop their respective scheduled tasks and running processes.Then, you will no longer deploy independent security CMS binary files for them.Instead, in the default site management backend's 'Multi-site Management' feature, these old sites are re-entered in the manner of 'Add New Site'.During the addition process, you need to accurately fill in the original root directory, website address, and database name and account information of these sites.Due to the design of Anqicms 3.x, it can automatically inherit the data of the old sites, ensuring seamless data migration, so these sites will not enter the initialization installation steps after being added to the new multi-site management architecture.
This process completed, all the original 2.x sites will be unifiedly managed by a 3.x version of the Anqi CMS core service.
The specific impact on the operation of existing sites.
This upgrade will bring a series of positive impacts to multi-site operations:
first, Deployment and maintenance will be greatly simplified. The mode of independently deploying and maintaining code for each site will be eliminated in the past.After the upgrade, all sites are managed by a core service, and daily operations such as system updates, backup recovery, and so on can be carried out centrally, significantly reducing the complexity of operations.No longer need to configure an independent startup script for each site, also avoids port conflict issues.
secondly,System resource efficiency is expected to improve. A single AnQi CMS process manages multiple sites, and compared to multiple independent processes, it usually uses the server's memory and CPU resources more effectively.This is particularly beneficial for users with a large number of sites, which may mean that they can host more sites or achieve better performance under the same hardware conditions.
Moreover,The uniformity of operational operations will be enhancedFor example, the document mentions that version 2.x does not support background restarts, while the centralized management mode of version 3.x allows all background functions, including system restarts and version upgrades, to affect all managed sites, improving the flexibility and automation of operations.
InData migration and compatibilityOn the one hand, you have nothing to worry about. The upgrade guide clearly states that when adding an old site as a new site, by specifying its original root directory and database information, the system will automatically inherit the data.This means that your content, users, configuration, and other core data will be retained and will not be lost during the upgrade process.
As forTemplate and feature compatibilityDue to the upgrade from 2.x to 3.x of AnqieCMS, the focus is more on the optimization of deployment and management architecture, rather than on large-scale functional reconstruction or revolutionary changes in template syntax (for example, version 2.1.1 has rewritten template tags, and model features have also been introduced), therefore, the templates and core functions of existing sites can usually maintain compatibility after the upgrade.If there are some custom templates that may need to adjust the static resource references according to the path after the Go project deployment, but the overall migration cost is relatively low.
In summary, the upgrade from AnQi CMS 2.x to 3.x marks the era of multi-site management becoming more centralized and efficient.Although it requires an initial one-time integration configuration according to the guidelines, in the long run, this will greatly simplify your website operation and lay a solid foundation for future expansion.
Frequently Asked Questions (FAQ)
1. Will my website data be lost after upgrading to AnQiCMS 3.x?Will not. AnqiCMS 3.x took data compatibility into consideration during its design, especially when integrating 2.x multi-sites into 3.x management. You will add them by specifying the original database and site root directory of the old site.The system will automatically inherit and utilize these existing data without the need for reinitialization, ensuring that your content, users, configurations, and other data are retained in full.
2. Do you need to modify the URL structure and template of the existing website after the upgrade?In most cases, the URL structure and template do not require large-scale modifications.The upgrade of AnQi CMS 3.x focuses mainly on the optimization of the underlying deployment and multi-site management architecture, rather than on fundamental changes to the front-end display or template syntax.If your custom template hardcodes old ports or paths (which may occur in 2.x multi-site environments), after integrating into the unified 3.x Go project management, minor adjustments may be needed to adapt to the new URL generation rules or static resource paths.It is recommended to test the key pages of each site after the upgrade.
3. Why is it simpler and more efficient to deploy multiple sites with AnqiCMS 3.x version?AnQi CMS 3.x introduces a unified Go project deployment mode, which enables all sites to be centrally managed by a core AnQi CMS service process.This is different from the way each site runs as a separate process in version 2.x.This centralized management model reduces redundant deployment and configuration work, reduces server resource consumption, and simplifies daily maintenance, upgrade, and restart operations, making multi-site deployment and management simpler and more efficient.