How to organize a remote team on a web project?

Question

HTML

There is a situation - php+html+css+js project (website) located on the server.
There are different people who perform tasks on the site directly on the server.
There is a problem - different people can edit the same files at the same time, while there is no file locking system.
How to organize access for different people to edit files and prevent the ability to edit the same files?
We tried SVN, but you need to edit the files directly on the server (without checkout), because there is no way to upload the site on the local computer (you need a web server).
What approach will help us?

Answer 1

1 Make test servers for everyone and still tie at least svn.
2 Different people perform different tasks but edit the same files? There is something wrong with your project architecture.
3 Use editors that warn you that the saved file has changed after opening. I like Komodo Edit (because that's how I am - too lazy to raise svn, and often something is wrong with the architecture of projects ;) )

Answer 2

git
autodeploy to test server

Answer 3

We tried SVN, but you need to edit the files directly on the server (without checkout), because there is no way to upload the site on the local computer (you need a web server).

Unscrew someone's head, for example.
Take away everyone's access to the server.
Move the code to git (I recommend bitbucket, for starters).
Set up Jenkins - to deploy the site on commits to the production branch.
Build a Vagrant reference image and distribute to your developers along with git access.