As an experienced website operations expert, I am well aware of the importance of Nginx pseudo-static configuration for improving user experience and search engine optimization (SEO), especially in powerful management systems like AnQiCMS that support multiple site management.Static URLs not only make the URL look more concise and readable, but also make the search engine spider more friendly to crawl and index the content, thereby bringing better rankings.

When we configure the Nginx pseudo-static for the multi-site of AnQiCMS in such mainstream server management tools as Baota Panel, there are several key considerations that need to be carefully considered to ensure the stable and efficient operation of the website.

Understand the collaboration mechanism between AnQiCMS and Nginx

Firstly, we need to clarify that AnQiCMS is an application based on the Go language, which usually runs on a specific port (such as the default port 8001), and is served by Nginx as a reverse proxy to receive external requests and forward them to AnQiCMS for processing.Nginx acts as a 'gatekeeper' and 'router' here, not only responsible for distributing traffic, but also needs to correctly direct those dynamic links that look like static files (i.e., pseudo-static links) according to the rules we define, to the AnQiCMS application.

The Nginx configuration template provided by Baota panel usually includes a core reverse proxy setting. A typical AnQiCMS Nginx configuration snippet is as follows: 

location @AnqiCMS {
    proxy_pass http://127.0.0.1:8001;
    proxy_set_header   Host             $host;
    proxy_set_header   X-Real-IP        $remote_addr;
    proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;
}
error_page 404 =200  @AnqiCMS;
location / {
   try_files $uri $uri/index.html @AnqiCMS;
}

The essence of this configuration lies intry_files $uri $uri/index.html @AnqiCMS;anderror_page 404 =200 @AnqiCMS;In short, Nginx first tries to find if the requested URI corresponds to a physical file or directory (such as images, CSS, JS, etc. static resources).If not found, it will catch a 404 error and internally forward the request to the one named@AnqiCMSThe location block, which then proxies the request to the actual port where AnQiCMS is running (for examplehttp://127.0.0.1:8001）。So that AnQiCMS can receive and parse these 'pseudo-static' URLs.

The core considerations for multi-site pseudo-static configuration.

When configuring Nginx pseudo-static for AnQiCMS multi-site, we cannot just stop at the above basic configuration, but also need to consider the following key points:

  1. The selection of AnQiCMS built-in pseudo-static mode and its matching with NginxAnQiCMS provides various built-in static rule patterns, such as "number pattern", "model naming pattern", and "category naming pattern", etc., even supporting "custom pattern".These patterns determine the URL structure of AnQiCMS when generating page links in the background.

    For example, the 'model naming pattern' may generate/article/123.htmlor/product/abc.htmlSuch a link. Which pseudo-static mode did you choose in the AnQiCMS background, Nginx must be able to forward requests that match this mode correctly to AnQiCMS.If AnQiCMS has generated/news/latest.htmlThe URL, while Nginx simply looks up the physical file, it will inevitably lead to a 404 error. Fortunately, the abovetry_filesanderror_pageCombination, which can handle various static URLs generated by AnQiCMS well, as it will forward all requests that do not match physical files to AnQiCMS for processing.Therefore, the key is to ensure that the pseudo-static feature of the AnQiCMS background is enabled and choose the URL structure you wish.

  2. Refinement of Nginx configuration filesAlthough basictry_filesThe commands are very powerful, but in actual multi-site operations, we may still need to make some detailed adjustments:

    • Static file processing:Ensure Nginx can efficiently handle the static resources of a website (images, CSS, JavaScript).location / { try_files $uri $uri/index.html @AnqiCMS; }In this rule, Nginx will try to provide physical files first, which is crucial for reducing the pressure on the AnQiCMS application server. Please ensure that your static resources (such as/public/static/Content under in Nginx'srootpointed to correctly in the command, or AnQiCMS'sBaseUrlThe configuration is correct so that Nginx can find these files.
    • Processing of specific paths:If some of your specific paths (such as admin management paths/system/, API interfaces/api/) No need for AnQiCMS's pseudo-static processing, but it is processed directly by the AnQiCMS application, then the defaulttry_filesIt is usually capable. However, if there are special static directories or files, such as third-party plugins or verification files, make suretry_filesthese files are processed first in order.
    • Custom static rules:If you have enabled the "Custom Mode" in the AnQiCMS backend to create complex URL structures (such as those containing{module}/{catname}and `{