Version control for the working environment of the site

Question

Does anyone have experience using version control on a production website? Would it be a terrible idea to run a website from a repository? I just found an article, but I would like to hear your thoughts / comments.

Answer 1

Each production manager will tell you the same thing: VCS (D) does not have a place in the production environment.

Perhaps you can have one “deployment deployment” server in the production area, where you have VCS that allows you to view the correct delivery from this server too, to copy / rsync to the correct production server.

But on the servers themselves, you only have:

• the application itself
• monitor the process and report
• some diagnostic tools

The reason is that the more elements you have in your release environment, the more likely it is that one of these elements will go wrong. Adding VCS to the mix is ​​not worth it.

Answer 2

Makes imho meaningless - a cheap approach to people.

In larger scenarios, you have development / testing / production, so you control the version on the development side and then publish it for testing and production. There is no need to check version control when it comes to production. You save one or two fallback versions for quick rollback, but otherwise you don’t need to.

Answer 3

The way I always did this is to have repository checks in real time and in the test version. Then my workflow looks like this:

• make changes to my dev check
• commit changes.
• update test.
• make sure everything works.
• upgrade production.