AnQi CMS is an enterprise-level system designed for efficient content management. As an AnQi CMS user who is well-versed in user needs and proficient in content operation, I am very willing to give you a detailed explanation of the multi-site management capabilities of AnQi CMS and guide you on how to easily add and configure new sites in the background.
Secure CMS Multi-site Unified Management: Strategies for Efficient Operation
It provides a high-efficiency, low-cost solution that allows you to serve multiple independent domain names or subdomain websites on a single server using a single codebase.Each site can have independent databases, content, user, and template configurations, while sharing the powerful underlying functions of the Safe CMS system, such as SEO optimization tools, content collection, and security protection, thus ensuring the independence of each site and the safety of data, as well as the stability and scalability of the system.
How to Add and Configure a New Site on the Back-end
Add and configure a new site in AnQi CMS, which mainly involves two steps: the first is the reverse proxy setting on the server side, and the second is the specific configuration of the site in the AnQi CMS backend.These two steps together ensure that the new site can be accessed via an independent domain and has independent data management.
Server-side Reverse Proxy Settings
Before you can access the new site normally, you need to ensure that your server (such as Nginx, Apache, or Baota/1Panel panel) has configured the correct reverse proxy for the domain name of the new site. The role of reverse proxy is to forward external domain name requests to the specific port where the Anqi CMS is running (the default is usually)8001This allows multiple domains to share the same security CMS program instance, while each website has an independent access address for visitors.
For example, using a common panel like Baota, you need to create a new website in the panel and configure it as a reverse proxy. When setting up the reverse proxy, the target address should point to the local address and port where the Aiqi CMS is running, such ashttp://127.0.0.1:8001
Security CMS New Site Configuration
After completing the reverse proxy settings on the server, you can then proceed to configure the specific settings for the new site in the Anqi CMS backend.This process is intuitive and easy to operate, ensuring that the new site has an independent identity and data storage.
Please log in to the Anqi CMS backend using your main site administrator account.In the navigation menu on the left, find and click the "Multi-site Management" feature.After entering the multi-site management page, you will see a 'Add New Site' button, clicking it will open the configuration form for the new site.
In the popped-up new site configuration form, you need to fill in the following key information:
Firstly, specify a name for the new siteSite NameThis name will be used as the identifier for the backend management interface, helping you distinguish between different websites. Please fill in according to the actual situation.
ThenSite Root DirectoryThe setting.This item is crucial; it does not refer to the physical root directory of the Anqi CMS program, but rather the directory used by the new site for independent storage of cache, uploaded files, and other data./app/Start with it, and replace the dots in the domain name with underscores in the form (for example, if the domain name isdev.anqicms.com, then the root directory of the site can be/app/dev_anqicms_com). Make sure that this directory name is unique.
Continue filling in the new site'sWebsite address, which is the complete URL for users to access the new website, for examplehttp://dev.anqicms.com. This address must be consistent with the domain name you have configured in the server reverse proxy.
You need to set up a separate set of credentials for the new site.Administrator account and passwordThese credentials will be used exclusively for logging into the backend management interface of the new site, independent of the main site's administrator account, further ensuring security.