How to synchronize a project on CMS?

Question

PHP

Hello.
I was asked at work to develop a website on CMS 1c Bitrix. The project will be led by two programmers at once.
Previously, one project was led by one programmer. He deployed the project locally in Openserver (Xampp, Wamp) and did everything alone.
Now we need to synchronize the development between the two. There was no such experience before. So I ask for help.
I present my thoughts below.
What needs to be synchronized?
1. First, the code. Roughly speaking files. PHP scripts, css style files, html layout, templates, etc.
2. Database on Mysql. After all, Bitrix store news, settings and much more important things in the database. After all, this site will need to fill in the content. And the content of each proger must be synchronized too.
In the end, the Yiddish characters of infoblocks and news should be the same. They are stored in the database.
Thinking out loud.
Openserver is an isolated environment of apache, php, mysql.
The main feature of such assemblies is that you can copy the entire OpenServer folder and run it on any computer.
The database is stored in this folder. DBs are simply files on a hard drive.
Thought like that. One will deploy Bitrix locally on the OpenServer. Bitrix will create all system tables. Then the second one will simply copy the entire OpenServer folder. Files will be synchronized via Yandex disk or bittorentsync.
It also solves the debugging problem. After all, everyone will have their own local copy. If I understand correctly, when debugging, the Apache server is temporarily frozen. If they debugged the same site, they would interfere with each other.
What is the best way to organize all this?
Software to be used phpstorm
Version php 5.4x
Debugger xdebug.
OS Windows 8.1 x64

Answer 1

Make a public dev server. Install the reference web environment www.1c-bitrix.ru/products/env/ on it. Development on Bitrix is ​​perfectly segmented between programmers, without any git, it is enough to gather a team in advance and beat the project into black boxes and go.
the dev-server should be the same for all programmers, because then you will not dock the database from different dumps.

Answer 2

1) Tadammmmmmm
and this magic word is git =)
Sites are github.
But you need the possibility of private repositories.
Free at https://bitbucket.org/ .
2) set up a special server, at least remote, at least not, and remotely develop on it.
But here there may be problems with overwriting the neighbor's code.

Answer 3

Use git Luke!

Answer 4

1. git
2. mysqldump

Answer 5

Git + database migrations