The company has multiple nginx, including production and testing environments, and wants to build a centralized management platform.
The management platform needs to provide Web access. Development and operation and maintenance can add a second-level domain name by themselves.
In this case, it involves the configuration distribution and reload of multiple nginx to load new configurations. What technical solution is better to solve the configuration management and distribution?
There are not many configurations and relatively few modifications, so there is little need to consider performance.
We are currently considering using SaltStack for centralized management. Does this require SaltStack to provide an API interface for the management platform to access?
It feels like sending configuration to SaltStack from the web through API and reloading. The whole process is relatively long and troublesome.
I wonder if you have a simpler solution. grateful.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
There is a copycat plan: the development and operation and maintenance staff write an nginx server configuration file and upload it themselves, and then create a script for each nginx server to download and reload. Just do the download processing and failure logic well, it's simple and crude.