How to organize distributed development and testing of a web project on a server?

Question

Project management

Hello! You need to organize work on a web project for several people on one remote server. I'm doing this for the first time and I have one solution, but I don't really like it. I am sure that it is possible to do better, so I ask for advice from experienced people.
What is given: shared web server where testing is done, git on another remote git host with all codebase. Since there is only one server, and there are many developers, the only thing that comes to mind is to clone the git repository on the server and, when the git hosting repository changes, do a pull on the server. Thus, we always get the latest version on the server and do not have problems with conflicts between edits of different developers. The downside is that in order to test something, you need to upload changes to a remote repository, and then do a pull on the development server.
Firstly, it is tedious and not at all fast, because sometimes you have to do it after each edit, and secondly, the main repository is clogged with such temporary pushes. Alternatively, you can use branches. This partially solves the second problem, preventing temporary commits from getting into the main branch, but does not solve the first - it's still long. Raising your own server locally on each developer machine is not an option, because as part of the developers work on a part of the code that is in separate repositories, the entire codebase is not available to them, and without it, the server cannot be raised locally.
I am more than sure that the task is quite trivial, but I have not come across it before.
How do you solve such a problem?

Answer 1

Everyone has a web server on the local machine, the developer writes the module locally and then deploys it to the server using capistrano. I have demo data on my local machine and then when deploying capistrano sinlink to the real database

Answer 2

The option is good, but the project consists of a backend and a frontend. The backend is not available to all developers. This is the problem, that it will not work to start the server locally, because such developers simply do not have this part.

Answer 3

For example, solve using different branches for developers without access to all the code, a separate subdomain looks at each branch. He only has access to his folders