About automation tools

Flexible thinking:
OBT goes online, from the initial manual replacement of configuration files, to the final design of configuration modification tools (use show to specify the configuration items to be modified, path to specify the file path where these configuration items are located, temp to specify the file, and finally to modify the file by The flow overwrites the corresponding file under tomcat), puts the configuration changes of the entire application into the database, and executes the application configuration changes through the database script. Simplify the complicated online process to only need to back up the application package, back up the database, replace the application package, replace the database, and start. That's it.
Here at TMC, I don't know if it is still manually modified.
Regarding the implementation of the configuration modification file, there are two ways. One is to place the configuration file that needs to be modified in the temp folder, specify the encoding of the read file, and read all files in text type, as it is currently. The disadvantage is that if the template file is modified and you forget to update the corresponding file in the temp folder, the old file may replace the new file; the other is to use different parsers for different configuration files to read.