How do you manage projects with GIT (Bitrix)?

Question

git

We have many projects, mainly on Bitrix, as well as on CodeIgniter and other MVC frameworks. For some reasons (religious-ethnic) GIT is not used. I want to transfer all projects to work through GIT, with MVC frameworks it’s clear - the code of the framework / pictures / cache in gitignore, the rest we push, merjim.
But with Bitrix, everything does not seem so simple to me:
- firstly, no migrations;
- secondly, in order to develop locally, you need to have a copy of the entire code of the Bitrix itself, and there are a lard of files, and each project can be on slightly different versions and editions, so you won’t be able to symlink into the same folder with Bitrix;
I don't remember what else seemed like a problem.
Please tell me how to deal with these problems and add if there are any other pitfalls.
The fact that Bitrix is ​​a poop, we all know, but as they say, the client is blowing, and we are dancing, we won’t get rid of him in the near future.

Answer 1

first, no migrations

Alternatively, use - https://github.com/worksolutions/bitrix-reduce-mig...
We feed this to PhpStorm (Languages&Frameworks => PHP => Include Path) - https://github.com/Prominado-ru/bxApiDocs . It does not solve the problem of different versions, but so far there have been no problems with this)
All project code is only in/local/

Answer 2

I don’t understand how Bitrix differs from others.
What exactly religious considerations do not allow doing this in the case of Bitrix?
Actually from experience of a problem the same - how to transfer changes of a DB.
I used two options:
1 Naive-primitive: we simply duplicate all the database changes made on the test on the combat server by hand and that's it. We added a field on the test - we add it immediately on the combat one.
2 Versioned scripts for modifying the database - all changes in the structure of the database are made only through the API, with special scripts that, when making changes, also change the version number of the database in the settings. The current required number is stored in scripts. On each hit, it is compared with what is in the database, and if they do not match, the migration scripts for the database are launched, which make the necessary changes. A little bit of crap during development, but then you can roll a website onto a completely bare installation.

Answer 3

1) Synchronize the database. We are writing a simple bash script that downloads the database from the test server to the local one. It works well for a couple of minutes, if not a store for 50k goods. With a new development, it generally takes 30 seconds to
2) rsync the bitrix folder. The first time takes about 5 minutes. When updating the kernel, it takes 30 seconds. It starts a couple a month
3) rsync of public folders (upload)
3) All development is only in the local folder, which is under the git.
All commands can be written in one bash file and run from the console.