How to properly organize the work when developing a project by several people?

Question

PHP

Hello! Don't kick me if I ask stupid questions, I'm just just starting to delve into the whole kitchen.
The question is, how to properly organize the development of a project by several people from several places? (For example, two people work in the office and at home) After reading
the forums, I came to the conclusion that a version control system (git) is needed, ....
Taksss ... I'll just tell you how I see it, and you, dear experts, give a kick to right direction, ok? ATP))
I was not familiar with the git system until yesterday, there was simply no need, but then a need arose, I read a little and found it very useful for myself.
So, suppose each developer has the same set of software, git and phpstorm installed at each workplace (in the office and at home). A new project was created in phpstorm, and driven under git, and now the developer works in the office, commits to himself slowly, comes home, clones the project for himself, and works further from home and commits, and the second developer does everything the same. These developers have their own server, let's say a dedicated server, so here's how to upload project files there? put git on the server too and after the commit go to the server and clone? the only way? Or share your best practices, I'm interested in how someone organizes their working environment. Ra detailed answers I will be doubly grateful. Thank you!

Answer 1

Putting a new release on the server using git is considered not the best practice.
There are many services that help you get a fresh release from GIT and put the result on a production server, google "deploy php"
For example Deploy to multiple servers of php code

Answer 2

Each developer has his own "sandbox" - a web server and various utilities. Required - version control system, without it nowhere. Each developer works on a specific feature or functionality. Commits changes to its branch created for a specific feature. All one person is merging - a team leader, a senior on the project, call it whatever you want. Store all changes in a centralized repository. For Git, you can raise Gitolite, GitLab (here you need more hardware resources) or use services like GitHub - free if the project is public and paid for a private repository, or BitBucket is free for private projects for small teams.

Answer 3

git-flow