As an experienced website operation expert, I fully understand the importance of Nginx pseudo-static configuration for improving user experience and search engine optimization (SEO), especially in such powerful, multi-site management systems as AnQiCMS.Static page not only makes the URL look more concise and readable, but also makes the search engine spider more friendly to crawl and index the content, thus bringing better rankings.

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

Understanding the collaboration mechanism between AnQiCMS and Nginx

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

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 will first try to find if the requested URI corresponds to an existing physical file or directory (such as images, CSS, JS, and other static resources).@AnqiCMSThe location block, which then proxies the request to the actual port where AnQiCMS is running (for examplehttp://127.0.0.1:8001）。Thus, AnQiCMS can receive and parse these "pseudo-static" URLs.

Key considerations for configuring pseudo-static URLs across multiple sites.

When configuring pseudo-static for Nginx in the multi-site of AnQiCMS, we cannot just stay at the aforementioned basic configuration. We also need to consider the following key points in depth:

  1. AnQiCMS built-in pseudo-static mode selection and Nginx matchingAnQiCMS provides a variety of built-in static rules patterns, such as 'number patterns', 'model naming patterns', and 'category naming patterns', etc., even supporting 'custom patterns'.These patterns determine the URL structure that AnQiCMS generates when creating page links in the background.

    For example, 'Model naming pattern' may generate/article/123.htmlor/product/abc.htmlSuch a link.You have selected which pseudo-static mode in the AnQiCMS background, Nginx must be able to correctly forward requests that match this mode to AnQiCMS./news/latest.htmlThe URL, while Nginx simply looks up the physical file, that will inevitably lead to a 404 error. Fortunately,try_filesanderror_pageCombination, which can handle all kinds of static URLs generated by AnQiCMS very well, because it forwards all requests that do not match physical files to AnQiCMS for processing.Therefore, the key is to ensure that the pseudo-static feature of AnQiCMS backend is enabled, and to choose the URL structure you want.

  2. Refining the configuration of the Nginx configuration fileEven though the basics aretry_filesthe instructions are very powerful, but in the actual operation of multiple sites, we may still need to make some detailed adjustments:

    • Static file processing:Ensure Nginx efficiently handles the static resources of the website (images, CSS, JavaScript).location / { try_files $uri $uri/index.html @AnqiCMS; }This rule prioritizes the provision of physical files by Nginx, which is crucial for reducing the pressure on the AnQiCMS application server. Please make sure that your static resources (such as/public/static/The content below in Nginx'srootdirective is correctly pointed to, or AnQiCMS'sBaseUrlconfiguration is correct, so Nginx can find these files.
    • The processing of a specific path:If some specific paths of yours (such as background management paths)/system/,API interfaces/api/It is not necessary to handle the pseudo-static processing of AnQiCMS, but it is handled directly by the AnQiCMS application, then the defaulttry_filesEnglish version: Usually already competent. But if there are special static directories or files, such as third-party plugins or validation files, ensuretry_filesEnglish version: The order can give priority to these files.
    • Custom rewrite rule:If you have enabled the "Custom mode" in AnQiCMS backend to create complex URL structures (such as containing{module}/{catname}、`{