Under a multi-site deployment scenario, how can the `stop.sh` script ensure that only the AnQiCMS instance expected by the user is stopped?

AnQiCMS is an enterprise-level content management system designed for small and medium-sized enterprises, self-media, and multi-site management, with multi-site management capabilities as one of its core strengths.In practical operation and maintenance, especially when deploying multiple AnQiCMS instances on the same server to support more independent sites, how to ensure precise operations on a specific instance, such as stopping only the service the user expects, has become a key challenge.stop.shThe script effectively solved this problem in this scenario through clever design.

AnQiCMS multi-instance deployment strategy analysis

AnQiCMS provides a flexible multi-site deployment mode to meet different business needs.

The first mode is throughSingle AnQiCMS instanceCombine the "Multi-site Management" function of the background and direct different domain names to the same AnQiCMS service through Nginx or Apache reverse proxy.In this mode, an AnQiCMS process handles access requests for multiple sites.stop.shScript that will stop the entire AnQiCMS service process, resulting in all sites managed by this instance being interrupted simultaneously.This pattern is suitable for scenarios where resources are concentrated and uniform management and maintenance between sites are required.

The second mode, which is the focus of this article and the scenario to be discussed, is deploymentMultiple independent AnQiCMS executable files

stop.shThe core mechanism of accurate shutdown implemented by script

stop.shThe script can accurately stop a specific AnQiCMS instance,