What are the options for a frontend developer to test a local server?
Hello! My friend and I are currently working on a pet-project, but we are encountering difficulties when it comes to testing his work since the database is located on my computer.

Currently, he simply pushes updates, and I test them on my PC, which is quite inconvenient. We considered hosting the project on a free platform so that he can also access the database, but this approach is not ideal either. I am confident that there must be a suitable solution, but I am unsure where to begin looking.

There are a few options for a frontend developer to test a local server with a remote database. Here are some suggestions:

1. Tunneling tools: You can use tools like ngrok or localtunnel to expose your local server to the internet. These tools create secure tunnels that allow external access to your local server, including your database. Your friend can then connect to your locally hosted project using the tunnel URL.

2. Remote database connection: Instead of hosting the entire project on a free platform, you can consider connecting to a shared or remote database directly from your local development environment. Your friend can connect to the same remote database, and both of you can work with the same data. This way, you won't have to push updates, and your friend can access the database without hosting the project elsewhere.

3. Virtual Private Network (VPN): You can set up a VPN that allows your friend to connect securely to your local network. Once connected, your friend can access the local server and database just as if they were on the same network. This approach requires more setup, but it provides a secure and direct connection between your systems.

4. Cloud-based development environments: Consider using cloud-based development environments like Gitpod or CodeSandbox, which provide collaborative coding environments. These platforms offer features like live sharing and remote database connectivity, allowing you and your friend to work on the project simultaneously.

Remember to prioritize security and ensure that any remote access method you choose is properly secured to protect your local server and database.

Please note that these suggestions may require varying levels of technical knowledge and setup. Choose the option that best fits your requirements and skill level.

If the test task can fit within the constraints of a free or cheap VPS (around a few hundred dollars a month), then that would be ideal. Otherwise, you can keep one computer dedicated for testing purposes. However, it is necessary to have access from the opponent on this machine. This means that the computer needs to have a white IP address, even if it is dynamic (in which case, it can be bypassed using DDNS). Another option is to have IPv6 for both the opponent and yourself. Alternatively, you can install Teredo/Miredo, which provides an IPv4 tunnel with IPv6.

Another possibility is to use a "direct" VPN, although it may be difficult to break through a provider NAT in some cases. Lastly, you can consider using a VPN through a VPS if both parties are behind an impenetrable NAT. There are numerous options available, so make sure to do some research and explore what suits your needs best.

There is no problem with sharing access to the database using an IP address if your provider offers a white IP address service.

However, if you find it inconvenient to keep your computer turned on all the time, hosting can be a suitable alternative.

In addition, mysql databases can be utilized not only by renting a virtual machine, but also by employing a regular shared hosting. Another option is to utilize a pre-configured server that you can connect to.

It's worth mentioning that shared hosting provides a cost-effective solution for accessing and managing databases without the need for dedicated hardware.

As a frontend developer, there are several options available for testing a local server when the database is located on another computer. One approach is to use tools like ngrok or localtunnel, which create a secure tunnel to your local server and provide a publicly accessible URL that your friend can use to access the project. This way, your friend can interact with the project without having to push updates to your PC for testing.

Another option is to set up a virtual private network (VPN) between your computers, allowing your friend to securely connect to your local server as if they were on the same network. This would enable real-time testing without the need to host the project on an external platform.

Additionally, you could explore using a collaborative development environment such as Visual Studio Live Share or CodeSandbox, which enables real-time collaborative editing and debugging of code, allowing both you and your friend to work on the project simultaneously.

It's important to consider security and access control when implementing any of these solutions, to ensure that your local server and database remain protected. I recommend researching and experimenting with these options to find the most suitable solution for your specific needs and technical capabilities.


There are several alternative approaches to testing local servers, depending on the specific requirements and constraints of the project. Some of these approaches include:

1. Virtualization: Using a virtualization tool such as VirtualBox or VMware to create virtual machines that mimic the production environment, allowing for comprehensive testing of the server setup and configurations.

2. Containerization: Leveraging containerization technologies such as Docker to encapsulate the server and its dependencies in a lightweight, portable container, which can be easily deployed and tested across different environments.

3. Mocking: Creating mock server instances or using mock server libraries to simulate the behavior of certain components or services, enabling isolated testing of specific functionalities without relying on the actual server.

4. Remote Testing: Utilizing remote testing services or cloud-based testing platforms to perform comprehensive testing of the local server from a remote location, ensuring scalability and accessibility.

5. Continuous Integration/Continuous Deployment (CI/CD) pipelines: Integrating the local server testing process into CI/CD pipelines to automate the deployment and testing of server configurations, ensuring consistency and reliability of the testing process.