Is there a way to display the design to the client without uploading it to the hosting server? Can I easily set up a public server in a folder to avoid repeatedly uploading the design to the hosting server?
Yes, there are several ways to display the design to the client without uploading it to the hosting server. One approach is to set up a local development environment on your computer using tools like XAMPP, WAMP, or MAMP. These tools allow you to create a local server in a folder on your computer, which you can then use to host and showcase your design to the client.
To set up a local server, you would typically install one of these tools, configure the server settings, and place your design files in the appropriate folder. Then, you can simply share the local server's URL with your client, and they can view the design directly from their web browser without the need for uploading it to a hosting server.
Additionally, you can consider using tools like ngrok or localtunnel, which can expose your local server to the internet temporarily. This way, you can share a public URL with your client that allows them to view the design hosted on your local server without having to upload it anywhere.
details:
1. Local development environment: When setting up a local development environment, you typically install a web server software like Apache, configure it to run on your computer, and create a folder where you can place your design files (HTML, CSS, JavaScript, etc.). Once the server is running, you can access your design by navigating to a local URL (such as http://localhost:8888) in your web browser. You can share this URL with your client so they can view the design without uploading it to a hosting server.
2. ngrok and localtunnel: These tools allow you to temporarily expose your local server to the internet. After installing either ngrok or localtunnel, you start the tool and provide it with the port number that your local server is running on. The tool then provides you with a unique public URL that you can share with your client. When the client accesses that URL, their requests are forwarded to your local server, allowing them to see the design without uploading it.
The combination of browsersync and localtunnel is quite intriguing. During the layout process, browsersync can be used on its own, allowing you to share your work with team members or clients by sending them a link. They can then view your progress and provide feedback. What makes this setup even more interesting is that browsersync continues to function seamlessly even after you've shared the link. This means that both your browser and the client's browser remain connected, enabling real-time synchronization of actions such as scrolling and button clicks.
Essentially, you are able to see exactly what the client is seeing and can easily demonstrate certain features or functionalities. This setup can be particularly useful when conducting video calls or screen sharing sessions through platforms like Skype or Hangouts. The best part is that you don't need to worry about hosting, having a white IP address, or investing in high-performance hardware.
Please contact your service provider to inquire about the availability of a "white" IP address and how to obtain it. Setting up an HTTP server, such as Nginx, Apache, Lighttpd, IIS, etc., is usually straightforward, especially if you don't require any additional features.
In general, I suggest configuring a Git hook for automatic updating. However, if you prefer not to use or set up Git, there are ready-made programs available. For Windows, you can try this program (or search for alternatives, as there are many available). For Linux, you have several options:
a) Mount the FTP server in the file system
b) Use inotify
c) Write a short script that copies the modified files to FTP (you can skip point A and use a console FTP client)
Note: For security reasons, it is not recommended to host a web server on your personal computer for such purposes. Additionally, obtaining a "white" IP address usually comes at a cost. Configuring an auto-warm feature, especially for Windows, may be easier than dealing with an IP address.
P.S. If you still decide to host the web server locally, I would recommend purchasing a domain for $1 (any domain will do) to simplify the process. This will allow you to use subdomains for additional sites.