MySQL + GIT how?

Question

PHP

Writing projects using GIT is good and more or less clear to me. But at the beginning of development, I thought about how to store database versions, how to merge them with different developers, and so on?
Far from deviating from development, I would like to ask how you restrict some developers from certain files? There is only one repository and, as a rule, the whole project is there, respectively, each new developer receives full sources, what to do?

Answer 1

On the first question: https://phinx.org/
On the second question: if it is critically necessary, split the project (and the code, respectively) into subprojects.
Separately, the admin panel, separately the site, separately some kind of internal api with mathematics, etc.

Answer 2

Migrations are kind of like a version control system for your database. They allow the programming team to change the structure of the database, while at the same time remaining aware of the changes of other participants. Migrations usually go hand in hand with the table builder for easier handling of your application's architecture.
This is the start of the documentation on migrations in the laravel framework. I suggest that you familiarize yourself with them on his example. laravel.su/docs/5.0/migrations

Answer 3

Database versioning uses migrations and seeds.

Answer 4

As an option: store the database metadata in the form of a script. The developer makes changes to the structure - expresses the entire database into a script. Changes in the structure in this form are easier to monitor.
Limit by branches, each makes a piece of code in his own, then collect