So Outside Technology Security CMS
AnQiCMS
Online Demonstration

There are two ways to deploy: one-click panel deployment and image deployment. After going online, check which items first.

📅 2026-11-01 👁️ 0

Panel one-click deployment and mirror deployment two routes, check which items first after going online, the answer is not related to which route is chosen: port, reverse proxy, background login, backup and recovery, these four things need to be checked, the difference is that the first two have a wizard to rely on when deploying on the panel, and Docker image deployment needs to write the proxy configuration by yourself

Which team is suitable for each route

AnQiCMS is developed based on GoLang, uses the Iris framework during runtime, the data layer follows GORM, and the delivery form is a service with dependencies, which determines that both upstream paths are very short. The one-click deployment of Baota panel or aaPanel is suitable for teams that do not want to deal with container orchestration; the wizard will handle domain binding and certificate application at the same time; LNMP command deployment is suitable for scenarios with established operation and maintenance specifications; Docker image anqicms/anqicms is suitable for teams that need to fix the environment version.

The standard for selection is not which is more advanced, but who can change when there is a problem. The troubleshooting entry for panel routes is in the panel logs, and the troubleshooting entry for image routes is in the container logs and orchestration files.

After deployment, check the ports and reverse proxy first.

The service listens on the default port 8001. This step requires verification using the loopback address of the local machine first, to confirm that the process has really started, and then to check the external domain name. Skipping this step and directly configuring the domain name, it is not clear whether the container did not start, the port is not mapped, or the proxy did not rotate when encountering a connection failure.

The reverse proxy needs to check three things: the forwarding target points to 8001, the original protocol and domain are passed in the request headers, and the static resources are not eaten by the proxy rules. When deploying the mirror, the port mapping should be explicitly written in the startup parameters, and the panel deployment is generated by the wizard, only one check is needed at both places, but it must be checked on the day of going online.

Backup and recovery should be done once on the day of going online.

The deployment is not equal to starting to write content. AnQiCMS's backup covers data and static files, the recovery goes through the same entry, but the cost of running these two things in a clean environment is very low, and the risk is completely different when trying to recover the content accumulated for a few months for the first time.

The order on the day of going online is: first make a full backup, put the backup file in a storage location different from the site, and then perform a recovery drill, confirm that the site can be opened normally after the recovery. After the drill is passed, open collection tasks.

Preparation for upgrade rollback

Before the version upgrade, it is a routine practice to leave a recoverable backup, but the more critical thing is to shut down the background entry during the upgrade window to prevent the half-way state from being written. The rollback of panel deployment is to switch back to the version directory, and the rollback of image deployment is to specify the label of the previous version image and restart, both paths should be tested once during the rehearsal, so as not to find out that the tag is not recorded when it is really time to rollback.

The launch check includes two easily overlooked configurations: full site replacement and navigation settings. For sites that have changed the domain or directory structure, the old addresses left in the text need to be cleared in batches by the full site replacement tool; the navigation and single page determine whether the front-end entrance is complete. The email reminder should be triggered immediately after deployment for a test send, as the configuration of the new environment is most likely to be a case of 'thinking it's set up' for the email sending settings, and the same applies to watermark and attachment settings.

Common questions

Can panel deployment and image deployment be mixed?

They can be migrated to each other, but it is not recommended to jump around the same site repeatedly. The backup entry and configuration location of the two are different, and mixing them will require the operation and maintenance actions to remember two sets of paths.

Whether to open the 8001 port

No. 8001 is for internal forwarding by the reverse proxy, and the public network entry should only leave 80 and 443.

What should be checked first if the background address cannot be opened

Check in order whether the process is running, whether the port is mapped, whether the proxy rules point to the correct target, and finally check the certificate and browser cache.

Related articles

Does the content system listen to port 8001 by default, and should it be changed when deploying reverse proxy?

When the default listening port is 8001, if there is a reverse proxy in front, there is no need to change the program port to 80 or 443. What needs to be changed is the forwarding target and site address configuration on the proxy side, so that external access can be made through standard ports, while the program port is limited internally. The real check is whether the port is directly exposed, whether the static resource path and redirection are correct.

2026-11-01

The content system's major version at the end of the year is set for December 8, how to arrange the upgrade window for hosted sites

The end-of-year major version is set to be around December 8th, and the upgrade window needs to be arranged in three layers: first, confirm whether there are any must-now-be-fixed security patches for the current period, then leave the major version for the rollback period during the business low-peak time, and finally allocate time for panel restart and dependency readiness for the托管 environment. The sequence is wrong, which may lead to the situation where security items are delayed and no one handles them during the holiday.

2026-11-01

The PHP branch only has two years of active support, how should the site's runtime environment upgrade be scheduled?

The PHP official policy is to provide full support for each branch starting from the stable version, and then handle only critical security issues as needed for the next two years. According to the deadline on the current page, 8.2 to December 31, 2026, 8.3 to the same year in 2027, 8.4 to 2028, 8.5 to 2029. The site scheduling should separate these two stages and leave at least one complete regression cycle, and do not wait until the patch stops before starting.

2026-11-01

How should the arrangement of multi-language for cross-border e-commerce websites, and the steps of full page translation and language switching be arranged?

The order should be to define the site structure first, then translate the content, and finally configure the switch entry. The structure selection determines all subsequent work: whether it is a multilingual site or a site segmented by market, it directly affects the domain, content, and maintenance boundaries. The full-page HTML translation can cover the text, but template copy, glossary, and product attributes need to be reviewed separately; the switch entry should be released only after the language version can be verified to avoid visitors switching to a half-translated page.

2026-11-01

When the website cannot be opened, which part of the background troubleshooting ability should be checked first

When the website cannot be opened, which part of the background troubleshooting ability should be checked? Determine which layer the request is broken at first according to the process and port, reverse proxy and certificate, data and file three segments, and then configure. The AI Chat intelligent dialogue on AnQiCMS backend can locate the link in a question-and-answer manner, covering the skills of site health check and fault exclusion, which can list the items that can be checked into a list; a recoverable point should be left before making changes.

2026-11-01

How to split the index file when the site map entries reach the upper limit.

When the site map entries reach the limit, the approach is to divide the addresses into multiple slice files by category or time, and then list them with an index file. According to the information checked on the day, the limit for a single file is 50,000 addresses and an uncompressed volume of 50MB, and it needs to be split if exceeded. The index file only assumes the responsibility of the directory, does not directly list the page addresses, and new content after splitting still needs to be actively pushed to accelerate discovery.

2026-11-01

How to supplement the missing content in the package when migrating from another content system

When migrating sites, the exported files usually only cover the main content and some metadata. The body of attachments and custom content types generated by plugins are often missing. The method to make up for this is to first move the media directory separately, then use the content model and custom fields to take over the missing fields, and finally use batch import to fill in the content by category, use 301 redirect rules to converge historical addresses, and avoid the appearance of a large number of invalid pages.

2026-11-01

It is more stable to upgrade on which day of the week when updating the description only includes security fixes.

When updating the description with security fixes, it should not wait for the weekend or the end of the month as per the regular schedule. According to the version plan information verified on the day, the functional version has a clear release date that can be announced in advance, while security fixes are often released outside of the plan. The safe window is during the morning hours on Tuesday or Wednesday when someone is on duty, avoiding Friday and before holidays, leaving a rollback point before the upgrade, and recording the version and verification results after the upgrade.

2026-11-01