As an experienced website operation expert, I have accumulated rich experience in the practice of AnQiCMS, especially in the understanding of multi-site management and its background access mechanism.Today, let's delve into how the backend access address of a new site is determined under the AnQiCMS multi-site architecture, as well as how we can customize it flexibly.
Revealing the mystery of the AnQiCMS multi-site backend access address: Flexible Customization and Security Practices
In the list of powerful features provided by AnQiCMS, "Multi-site Management" is undoubtedly one of its core highlights.It allows enterprises and individuals to efficiently operate multiple independent websites under the same system, greatly enhancing management efficiency and resource integration capabilities.However, many operators often think about a seemingly simple but crucial question when deploying a new site: How is the background access address of the new site determined?This is not just about convenience of access, but also closely related to the website's security strategy.
AnQiCMS takes a design principle that considers versatility, customizability, and security in dealing with this issue, providing us with a clear and flexible solution.
Default rule: A starting point of simplicity and efficiency
Firstly, for any new site created on AnQiCMS, the backend access address has a default, unified rule:
Your website domain should be added after/system/The path.
For example, if the domain name of the newly created site isdev.anqicms.com, then the default access address of the back-end management interface ishttp://dev.anqicms.com/system/. This/system/The path is the standard entry set for all site backends within AnQiCMS, whether it is deployed through Docker, installed via Baota panel, or configured manually via command line, this default rule remains consistent.
The benefits of this design lie in its simplicity and clarity.The operation personnel do not need to memorize complex random paths, they just need to know their site domain and can easily access the backend.Also, this relatively unified naming also facilitates the maintenance and upgrade of the system itself.
Custom backend domain: dual protection of security and personality
AnQiCMS, as an enterprise-level content management system, fully understands the importance of security for website operation. Although the default/system/The path is convenient and easy to remember, but for operators who pursue higher security and brand professionalism, the ability to customize the back-end entry is undoubtedly a strong demand.
It is gratifying that AnQiCMS has considered this from the very beginning of its version iterations. According to our documents, AnQiCMS has added new features starting from version v2.1.1.Supports custom background domain function, enhances background protectionThis means that you can also use the default,/system/Path, you can also configure a completely independent backend access domain for each site, such ashttps://admin.your-new-site.com.
How to configure it?When you first visit the backend of a new site (at this time it is still新站点域名/system/）and complete the initialization settings, you can log in to the management backend of the new site. Find it in the left menu of the backend, and then go into“Backend Settings”，“and then enter into“Global Function Settings”Here, you will see a name as“backend domain address”The configuration option. You can enter the exclusive domain name you wish to use to access the backend of this site, for example,https://admin.mynewbrand.com.
Important reminder:Ensure that this custom backend domain has been correctly resolved (for example, an A record or CNAME record) and bound to your server before making this configuration. If HTTPS is used, the SSL certificate also needs to be properly configured.Otherwise, after the configuration is completed, you will not be able to access the back-end through this custom domain.
This custom mechanism not only improves the security of backend access (through domain obfuscation rather than simple paths), but also makes the website look more professional and personalized, avoiding the embarrassment of all site backends being the same.
Address management strategy under multi-site environment
When we use the "Multi-site Management" feature to add a new site in the AnQiCMS master control background, the mechanism of determining the background access address also follows the above principles, but adds an additional layer of "site isolation" logic:
- Domain Independent:Each new site created through AnQiCMS 'Multi-Site Management' will have its own independent website address (domain or subdomain), for example
siteA.comandblog.siteA.com. - Default backend entry:For each independent site, its backend access address is:Default pathare
您的独立站点域名/system/. That is to say,siteA.comEnglish version of the backend issiteA.com/system/,blog.siteA.comEnglish version of the backend isblog.siteA.com/system/. - Independent customization:What's more powerful is, AnQiCMS allows you toset it independently for each new siteSet its 'backend domain address'. This means,
siteA.comThe backend can be customized asadmin.siteA.comwhileblog.siteA.comThe backend can be customized asmanager.blog.siteA.com. All these customizations arein the backend management interface of each siteand they do not affect each other.
Therefore, in the multi-site management scenario, the background access address of the new site is first determined by itsfront-end domainand then supplemented by the default,/system/Path; you can optionally log in to the backend of the site, throughGlobal SettingsConfigure one for itA dedicated backend domain, thus achieving the maximum flexibility and security.
In short, AnQiCMS gives you complete control over the background access address, whether it is adopting a unified default path or customizing a dedicated entrance for each site, all aimed at making your website operation more convenient and secure.
Common Questions (FAQ)
Q1：After creating a new site, do I need to configure a reverse proxy for each site to access its backend?
A1:In most cases, the reverse proxy you configure for the new site (for example, to新站点域名Mapped to the 8001 port of the AnQiCMS instance forfront-end pageCan access normally. For background access, AnQiCMS will be under the same domain name (/system/Path) or you can handle the routing under the custom backend domain.Therefore, you do not need to configure a reverse proxy that is completely different from the front-end separately unless you have set up a completely new independent domain for the back-end, in which case you may need to ensure that this independent domain also correctly points to the AnQiCMS service.
Q2: If I customized the background domain address of the new site (such asadmin.newsite.com），then the originalnewsite.com/system/Can it be accessed?
A2：Once you set the 'background domain address' for a site in the AnQiCMS background and it takes effect, the system will usually respond to the new custom domain first. To enhance security, the original新站点域名/system/The path may be restricted, it may be redirected to a new domain name, or access may be directly denied.This is a measure taken by AnQiCMS to enhance backend protection. It is recommended that you only access the backend through the custom backend domain you set.
Q3: Can I set a unified backend access address for all the multi-sites of AnQiCMS, likemanage.myserver.com/site1//manage.myserver.com/site2/this form?
A3:AnQiCMS in design, each site tends to usean independent domain or subdomainAs its identification identifier, and the default background access address is also based on this independent domain name. Although you can try to achieve this through more complex path rewriting rules of external servers such as Nginxmanage.myserver.com/site1/This form, but this usually requires modifying the AnQiCMS underlying logic for site recognition, and not