There is a question that has been bothering me:
We have installed the git service in both the production environment (a) and the test environment (b). When we were developing, we used the develop branch on b ( A local submission will be submitted to b's remote develop, and then automatically synchronized to b's web server ). To go to the production environment, we merge from develop to the master branch locally ( add a remote source to the local master, and then git push production (remote source name) master ). This method is very troublesome when the configuration files are constantly changing due to different environments. How do you deal with the git workflow?
For details on the team’s continuous development in development, testing, simulation, and production environments, please refer to the technical team code management and deployment
It is also recommended to use the online deployment system WALLI developed by our team. Learn more on the homepage.
Don’t put the configuration file directly in the repository. You should store a copy, such as db.config.example. When deploying the environment, you will manually copy a db.config and modify the content, and local development will put db.config in the ignore list. .