Where and how to store the layout of pages when working with GIT?

Question

git

There is a project on ROR.
Several programmers and web designers are working on it in a distributed manner using GIT, where it works. Everyone has their own local copy of the project.
Content and layouts, chunks, page partitions are stored in the database. Because of this, conflicts arise, in that developers always have different content on their machines, in production, etc.
The option proposed by the programmers is to make migrations every time the content changes. But in my opinion it is difficult for layout designers, and it will also take a lot of time, instead of just making changes to the admin panel and forgetting about it.
How to correctly and easily build an exchange of content that is stored in the database?
How should a page be stored in a project in general, what is in the database, what is in the code? - all page templates in files
Where can I read about all this? - unanswered question( I don't even know what to look for.
Thank you!

Answer 1

I'm not a rogue, but I would beat hands for storing templates in the database. It's forgivable puffygogovnotsms, but right? What made you come up with this idea?
And yes. Migration is probably best - nothing needs to be edited through the admin panel.

Answer 2

The structure is in the code, the content is in the database.
If there is some reference content, then using the git pull hook, you can update the database from certain files with the desired content.

Answer 3

When I worked at VimpelCom, the sites also stored templates in the database there.
The system administrators answered that they say that access to templates from memory is faster and there are no unnecessary requests to files on the server. to xdd.
but it seems to me that everything is solved by stupid caching, even if in the same muscle

Answer 4

Move all templates to files, otherwise this hemorrhoids will last forever