Answer the question
In order to leave comments, you need to log in
Git. Dev, prod server. config storage?
Good day to all.
Please tell us how you organize the logic for storing configs in the Gita.
If you do a dev server and production, then what about the configs? Let's say that the production has its own config for the database, radish, for Devs their own, the developers on local PCs have their own.
On the dev and production servers, the configs were already there before me, I thought that I would just add them to the gitignor and there would be no problems. However, git still keeps track of their changes, and when you commit, they indicate them (modified state). What is the right thing to do in such a situation?
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question