How to organize development with a version control system?

Question

git

I'm a manager. There are several employees in subordination, in particular layout designers and programmers. We are supporting projects. Those. often the task is to draw, make up, fasten and transfer. Several such tasks per day.
It would be desirable, that there was a control of changes. Those. it was clear what, when and when they changed. And, of course, the possibility of rollback.
The company has a development server. After making changes, they are transferred to the hosting. Those. site in 2 versions: local and production. It turns out a difficult path: set up a web server on the machine, take a copy to yourself, install somehow on your web server, upload the changes back. And how can he drive the database back and forth?
How to deal with text files is approximately clear. And what about the DB?
We have a server under linux, all workstations under win, editors from JetBrains
If it is not clear, please ask clarifying questions.

Answer 1

Capistrano github.com/capistrano/capistrano
does a good job of updating and auditing with the possibility of rollbacks . There is also a special task for applying database migrations.
Don't worry that it's in ruby, we use it with php projects without any problems

Answer 2

The developer has a local database - the developer himself rolls changes on it with his hands, and other developers with the help of migrations.
A database on a common dev server (if any) to which changes are rolled
by database migrations on a production server - migrations from the master branch are also rolled.
You will only have to choose a convenient way for you to manage migrations. Many frameworks have built-in tools for migrations.

Answer 3

1. To track changes in the database by several developers, use deltaSQL
2. To manage projects and sources, I strongly advise you to buy licensed JIRA and Fisheye (the price for both products is $10 for 10 developers)
3. If for some reason item 2 cannot be implemented , then use the similar service bitbucket.org It allows you to open private repositories for free. First, register yourself, and then send invites to your employees - this will increase the number of free users who can work on your projects.
In general, setting up a workflow is a separate and complex topic. It is desirable that one of the employees was engaged in this process purposefully. For example, a special person who understands what he is doing and, in which case, will be able to fix the jambs that will inevitably happen in the process of releasing new versions, should update production servers.
PS. In no case do not develop on production servers! All the same environment can be configured under Windows.

Answer 4

Thanks for answers. Some have adopted. It’s complicated, I’m still a manager)
Do I understand correctly that if the team is working on one site (we all have commercial CMS clients), then before making changes to the site, the developer must take a copy of the site from the dev server to himself (install it on his local server)?
If yes, then that is the problem. The projects are all on the dev server, and they do not want to set up a local server and take the project to themselves along with the database and content. Are there other workflow options?