What is your process for developing a site (opencart) using git? How do you sync a db in git? What do you close in .gitignore for opencart?

Question

git

The main task: to establish the development of an online store (opencart) by 2-3 developers. Developers do not work under the same roof.
Emerging questions:
1) How does the process of creating an online store go for you? What teamwork tools do you use?
2) Working with git. Is it possible to somehow automatically push changes to the main branch to some hosting thread, where this branch can be viewed by developers and customers? By type of commit to the remote repository. After all, we have a working version of the site in the same Bitbucket. But we can see these files "in work" either locally or by uploading via the same ftp (which is not very convenient). For example, I heard that phpstorm has the ability to commit and immediately send a file via ftp to a test domain / hosting.
3) How do you synchronize the DB? After all, I can change my database, but the rest will not know about my changes ... And every time I need to export / import it, which is also expensive.
4) What do you close in .gitignore for opencart?

Answer 1

opencart is not intended for normal
git development, migration, testing - not about this craft

Answer 2

I can’t speak for opencart and git, but we use hg at home (I think it’s also possible on git) and the process looks something like this:
There are two domains on the server - main and test.main. All pushes go to test.main, it has a hook configured to change the repo, which pushes everything to the main.
On test.the main branch is always a test, on the main default.
Now we are crawling to bitbucket for Code Review, there will be a hook that pulls the domain, then on the server, then pull from the bitbucket and push to the main one. Something like this.
2. You can automatically, look in the direction of the hooks, you will have a repo there, but always on the same branch. FTP would generally not recommend using for file synchronization.
3. DB yes, we have a problem with it, we agree, we carry backups, but for good it's worth adding a migration system.
4. I can't help)
PS Hooks are also set up so as not to commit directly to the test, not to let it be merged from the test into the main branch or the one being developed, only you can pour it into the test. Another hook for not committing to default directly, just merge. And also so that the test cannot be merged with the main branch