A
A
Alexander2019-09-06 12:30:20
Work organization
Alexander, 2019-09-06 12:30:20

How can multiple developers work on the same site?

Hello!
It became interesting how the work of several developers to finalize sites is organized.
Until now, I have been working alone on the project and the work was carried out as follows:
I connected via ftp to the site server, edited the file and uploaded it back. Refinement was carried out on the "combat", because. the edits are small and it took longer to load the entire site.
And now it turned out that me and a colleague need to work on one site. And here we are, periodically stipulating who edits which files, trying not to overwrite each other's changes.
And the essence of the question: how is this kind of work organized in general? I have never worked in a team with more than one person (me) and have no idea how 3 developers work on one site.
Thank you!

Answer the question

In order to leave comments, you need to log in

3 answer(s)
L
Lazy @BojackHorseman, 2019-09-06
@Alexandros96

version control systems. e.g. git

M
managrib, 2019-09-06
@managrib

differently.
if two - it is easy to coordinate, not much different from "in one".
if everyone has their own field of activity (separately backend, separately frontend), then in fact these are different projects. they have only 1 point of contact - the API
to make changes through git / etc is recommended even when working "in one".
well, for the group it is all the more practical - you never know who will make incompatible changes there (not out of evil, but out of carelessness), you can find them.
rolling out to a production server - in the simplest case, makes 1 responsible
in a more modern and more sophisticated version with DevOps - anyone can deploy using a configured deployment system (in the simplest case, Ansible / etc)
the question is too general, therefore the answer is general.
ask more specific questions.
PS:
If you want the software to do everything for you, then rely on PaaS + Git (for example, Heroku + BitBucket)

M
marataziat, 2019-09-06
@marataziat

See what Git and Github are, you can now commit your project and then go to different branches to create features, etc., that is, you must go to your code folder and do

git init
git add .
git commit -m "inital commit"

Потом когда вы создадите репозеторийй в Github будет инструкция как добавить remote origin и запушить код

Next you do:
git checkout -b alexandr

После изменений делаете 

git add 
git commit -m "добавил админку"

And your colleague should also do only git checkout -b to put a different name, after pushing you will have to do git merge, git pull, etc... but you will already be told about this in Git lessons :)

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question