How is the backend access address determined for a new site in the AnQiCMS multi-site management?

As an experienced website operation expert, I have accumulated rich experience in the practice of AnQiCMS, especially in the deep understanding of multi-site management and its background access mechanism.Today, let's delve into how the background access address of a new site is determined under the AnQiCMS multi-site architecture, as well as how we can flexibly customize it.

Unveiling the mystery of AnQiCMS multi-site backend access address: Flexible customization and security practices

Among the powerful features provided by AnQiCMS, 'Multi-site Management' is undoubtedly one of its core highlights.It allows businesses 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 backend access address of the new site determined?This is not just about the convenience of access, but also closely related to the website's security strategy.

AnQiCMS has adopted a design principle that takes into account universality, customizability, and security in handling this issue, providing us with a clear and flexible solution.

The default rule: a concise and efficient starting point

Firstly, for any new site created on AnQiCMS, the backend access address has a default, unified rule:

Add your website domain name to/system/the path.

For example, if the domain name of the new site you created isdev.anqicms.comThen the default access address of the background management interface ishttp://dev.anqicms.com/system/. This/system/The path is the standard entry set internally for all site backends in AnQiCMS, whether it is deployed through Docker, installed via Baota panel, or manually configured via command line, this default rule is consistent.

The benefits of this design lie in its simplicity and clarity. Operators do not need to memorize complex random paths, they just need to know their site domain name to easily access the backend.At the same time, this relatively unified naming also facilitates the maintenance and upgrade of the system itself.

Custom backend domain: dual protection of security and individuality

AnQiCMS, as an enterprise-level content management system, 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 background entry is undoubtedly a strong demand.

It is pleasing to see that AnQiCMS has already considered this in its version iterations. According to our documentation, AnQiCMS has added this feature since version v2.1.1.“Support custom backend domain function, enhance backend protection”. This means that you can also use the default/system/The path, you can also configure a completely independent backend access domain for each site, for examplehttps://admin.your-new-site.com.

How to configure it?When you first visit the backend of a new site (which is still新站点域名/system/After completing 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 go into“Background Settings”, then enterGlobal function settings. Here, you will see a name called'Backend Domain Address'The configuration item. You can enter the exclusive domain name you want to use to access the site backend, such ashttps://admin.mynewbrand.com.

Important reminder:Before performing this configuration, you must ensure that this custom backend domain has been correctly resolved (e.g., A record or CNAME record) and bound to your server, and if HTTPS is used, an SSL certificate also needs to be configured.Otherwise, after the configuration is complete, you will not be able to access the back end through this custom domain.

This custom mechanism not only enhances 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 that all site backends are the same.

Address management strategy in a multi-site environment

When we use the "Multi-site Management" feature to add a new site in the AnQiCMS master control backend, the mechanism for determining the backend access address also follows the aforementioned principles, but with an additional layer of "site isolation" logic:

1. Domain independent:Each new site created through AnQiCMS "Multi-Site Management" will have its own independent website address (domain name or subdomain), for examplesiteA.comandblog.siteA.com.
2. Default backend entry:For each independent site, the background access address isthe default pathare您的独立站点域名/system/. That is to say,siteA.comthe background issiteA.com/system/,blog.siteA.comthe background isblog.siteA.com/system/.
3. customized independently:What is more powerful is that AnQiCMS allows you to seteach new site independentlyits "backend domain address". This means thatsiteA.comthe backend can be customized asadmin.siteA.comwhileblog.siteA.comthe backend can be customized asmanager.blog.siteA.com. These customizations are allEach site's backend management interfaceBeing carried out, affecting each other.

Therefore, in the scenario of multi-site management, the backend access address of the new site is first determined by itsfront-end domainand then supplemented by the default/system/Path; thereafter, you can optionally log into the backend of the site throughGlobal SettingsConfigure one fora dedicated backend domainto achieve maximum flexibility and security.

In short, AnQiCMS gives you complete control over the background access address, whether it is using a unified default path or customizing a dedicated entry for each site, all aimed at making your website operation more intuitive and secure.

Frequently Asked Questions (FAQ)

Q1: After creating a new site, do I need to configure a reverse proxy for each site to access the backend?

A1: Generally, you configure a reverse proxy for your new site (for example, to新站点域名Mapped to the AnQiCMS instance on port 8001 is tofront-end pageCan access normally. AnQiCMS will access the same domain name for background access (plus/system/Path) or handle routing under your custom backend domain.Therefore, you do not need to configure a separate reverse proxy for the backend that is different from the frontend, unless you have set up a brand new independent domain for the backend, in which case you may need to ensure that the independent domain also correctly points to the AnQiCMS service.

Q2: If I customize the background domain address of the new site (such asadmin.newsite.com），then the originalnewsite.com/system/Can you access it?

A2: Once you have set the "background domain address" for a site in the AnQiCMS backend and activated it, the system will usually respond to the new custom domain first. To enhance security, by default, accessing the original新站点域名/system/The path will be restricted, may be redirected to a new domain, or directly denied access.This is the measure taken by AnQiCMS to achieve "enhanced backend protection", it is recommended that once you set a custom backend domain, you should only access the backend through that domain.

Q3: Can I set a unified backend access address for all multi-site AnQiCMS, such asmanage.myserver.com/site1//manage.myserver.com/site2/is this form?

A3: AnQiCMS is designed in such a way that each site tends to useindependent domain name or subdomainAs its identification mark, and the background access address is also based on the independent domain by default. Although you can try to implement more complex path rewriting rules through external servers such as Nginx.manage.myserver.com/site1/This form, but this usually requires modifying the logic of AnQiCMS to identify the site, and not