So Outside Technology Security CMS
AnQiCMS
Online Demonstration

BaoTa one-click deployment AnQiCMS: from Docker image to production environment

📅 2026-11-01 👁️ 0

How to quickly deploy AnQiCMS to a production environment on Baota panel or aaPanel? First, take a look at the system's program form: It is a single-program content management system written in GoLang, using Iris as the framework, GORM for the persistence layer, does not require an additional PHP runtime, and can be up and running without depending on external caching services.What is meant by 'one-click deployment' is that the panel combines the steps of downloading the program, creating the database, starting the process, and configuring the reverse proxy into one execution; if the panel is not part of your operational habits, using the Docker image or LNMP command route will still lead to the same production environment.

Three things need to be determined before deployment.

The first is the entry port. The program listens on port 8001 by default, and external access requires the site software or reverse proxy to forward ports 80 and 443 to this port, and the panel route is usually automatically written for this forwarding.The second is the database. GORM is responsible for the data layer, set up the database and account first, then start the program, to avoid leaving half of the configuration due to connection failure during initialization.The third is the backup person responsible. Backup and recovery are paired functions in the background, and data along with static files are included, but the triggering time still needs to be arranged by humans: whether it is done once a day on a timed basis or manually done before each upgrade, the difference in operation and maintenance intensity between these two routes is very large.

Deployment route Who is it suitable for Points to note when getting started Rollback method
One-click deployment with Baota panel Domestic teams using panel to manage servers After installing the site software in the panel, execute one-click deployment, and the forwarding rules are generated by the panel Panel snapshot and background data backup
aaPanel Overseas servers or English panel environment The process is consistent with BaoTa, pay attention to certificate and port forwarding configuration by the panel Panel snapshot and background data backup
LNMP command deployment get used to command line operations manually configure Nginx reverse proxy to point to 8001 and self-sign certificates manually backup configurations and data
Docker image aim to containerize deployment or achieve consistency across multiple environments pull the anqicms/anqicms image, map ports and mount data volumes switch back to the previous image tag

actual operation sequence of the panel route

Create a new site and bind a domain on the panel, then install the site software and database, and then execute the one-click deployment action. The panel will follow this chain of operations: 'download program, initialize database, start process, write reverse proxy', until the homepage of the site can be opened, indicating that the forwarding of port 8001 has taken effect. The remaining three things need to be manually confirmed: whether the certificate has been issued and强制 redirected, whether the backend entry adheres to the site's own access conventions, and whether the attachments and static files are within the scope of backup and recovery.

On the overseas server, the aaPanel process is consistent, with differences concentrated in the default strategy of certificate issuance and port forwarding. If the server has a firewall or cloud security group, you need to forward the port separately outside the panel, otherwise, the local test is normal and the external network access times out.

Pay attention to the boundaries of the command walking route.

LNMP deployment is suitable for teams that already have unified operation and maintenance specifications. The key points are to write clear forwarding rules for the site software, point to port 8001, and confirm the read and write permissions of static resources and upload directories. When upgrading, retain the program files and database backups of the previous version, and you can revert to the old program directly if an exception occurs. The Docker route fixes the version on the image tag, which is better for consistency across multiple environments, but the cost is to maintain data volume and configuration persistence yourself, and do not write data to the container file system.

If you still don't want to go directly to production, first use the online experience station to familiarize yourself with the backend structure and then decide on the deployment path. The backend entrance of the experience station is consistent with the official site, after going through the release and backup process, the judgment at the time of deployment will be more accurate.

Common questions

What should you check first if you can't open the page after deployment?Check the two segments of port forwarding and reverse proxy: can the local machine access 8001, and is the forwarding rule of the site software pointing to it?

Can panel one-click deployment and Docker be mixed?It can be evaluated separately: the panel route is convenient for operation and maintenance takeover, the Docker route is convenient for version rollback, and it is clearer to choose one main route for the same site.

How do I migrate the data?Use the backup and restore function in the background, process the data and static files together, and check the attachment references after migration.

What should I do if the upgrade fails?First, restore the previous backup, then check the version number, and do not repeatedly execute the upgrade action under the failure condition.

Related articles

Scheduling release and recycling station: automation and fault tolerance of the content workflow

Scheduling is solved by time factors, error tolerance by the recycle bin: AnQiCMS divides documents into four states: formal documents, drafts, pending release, and recycle bin. Timely publication allows content to automatically become formal at the agreed time. Deleted formal documents can be recovered by entering the recycle bin, and drafts with the link preview=true can be previewed. With the cooperation of both, the content team does not need to rely on manual monitoring, and publication accidents can be rolled back within a few minutes.

2026-11-01

Scheduled releases are set for two o'clock in the morning, and who is in charge of the content launch process?

The scheduled release at 2 o'clock in the morning cannot rely on human guards. The time factor is only responsible for going online on time, not for the quality of the content; the real control is the status transition and content review before release: drafts are responsible for writing, to be released for review, sensitive word filtering and keyword replacement are supported at the system level, and then the authority decides who can put the manuscripts into the to be released queue.

2026-10-26

What method should be used for batch importing articles, and what scenarios do the interface and backend manage?

There are two ways to batch import articles: the background batch import of manually organized ZIP archives and Excel spreadsheets, suitable for one-time content migration; the document content import interface /api/import/archive is suitable for programmed content production and scheduled synchronization, you can check whether the title already exists before writing to avoid duplication. Check the title, category, tags, and fields before migration, and review the landing pages and links by category after migration.

2026-10-26

The test version announcement is only suitable for test environments, and how to set up a pre-release site.

Announcement of the test version written by oneself, 'Only suitable for test and development environments', means that a pre-release site with the same version, configuration, and data form as the official site is needed to carry out verification. The method is four steps: copy data副本 from the official library, replicate the environment according to the configuration of the official site, isolate the verification content with drafts and pending release status, and synchronize the conclusion to the official site after acceptance.

2026-10-26

Why Static URL and 301 Redirect are the Infrastructure of Enterprise SEO That Cannot Be Neglected

Static URL determines how the URL looks and whether it can be reliably indexed, while 301 redirect determines the weight of the old link and whether visitors will lose after the address changes. Enterprises consider these two items as infrastructure because once the address rules change after the growth of columns and articles, the impact is the entire site rather than a single page. It is recommended to first define the static URL rules, then converge the historical addresses, and finally check whether the sitemap and push are synchronized.

2026-11-01

Use anchor text management to enhance on-site SEO weight transmission

Anchor text is the segment of text within an internal link, which determines how a search engine understands the theme of the page being pointed to. This article explains how to establish a keyword library, automatically add anchor text links to in-site keywords, control duplicate anchor text and link density, let the weight pass along with content relevance, and provide the steps and self-checking method for over-optimization of AnQiCMS anchor text management.

2026-11-01

Practical configuration of static URL and 301 redirection

The static page makes the dynamic page accessible with a standard and readable address, and the 301 redirect converges the old addresses left by the revised or changed column to the new page. This article explains in order how to configure it in AnQiCMS: first, enable the static page rules in the background and unify the address style, and then use the 301 redirect to manage old links, and provide troubleshooting methods for common problems such as circular redirection and rule failure.

2026-11-01

How to configure content security audit on the corporate website, how to configure AnQiCMS's sensitive word filtering and reCAPTCHA?

How to prevent malicious content and robot submissions on the corporate website, it can be configured in three layers: 'Interception before submission, review before storage, and account layer protection': AnQiCMS's sensitive word filtering and keyword replacement are responsible for text control before storage, content review process controls the release gateway, form integration with reCAPTCHA verification code blocks robot batch submission, JWT authentication and prevention of SQL injection, XSS ability to guard accounts and interface layers. This article provides the configuration sequence and checklist.

2026-11-01