Keep servers running smoothly by using command-line tools and automation scripts.
Keep servers running smoothly by using command-line tools and automation scripts.
I aim to set up a lightweight Debian server on an old machine with 8GB DDR3 RAM. I plan to run everything from the command line to conserve resources for hosting multiple sites on this future self-hosted web server. How can open source tools help run an HTTPS site without spending money beyond hardware costs? Programmers still manage servers using only command-line commands, similar to MS-DOS days.
Debian and similar Linux distributions along with web servers are built for command-line configuration. There are plenty of tools available, though some overlap exists in minor areas. While programmers aren’t usually seen managing servers, maintaining them often relies on commands and scripts. It’s best to keep your website separate from the production server environment. Use a distinct test setup instead of connecting it to the live box.
You should handle your deployment separately from development. Keep your code elsewhere and establish a method to push your finished work to the server—whether through simple FTP transfers, service restarts, SSH connections, or advanced tools like Git sync. Hosting static sites doesn’t require much power. There are countless options available. For basic needs, a simple nginx configuration works well. It’s practical for small projects. For bigger projects, you typically rely on automated workflows with CI/CD pipelines and web interfaces to manage updates. A "finished website" can be as simple as HTML and CSS with no extra features. You can transfer it in many ways—via SSH, FTP, or even a USB drive.
I rely on webmin and cockpit for routine upkeep, while setting up a GUI for initial setup and changes. After that, I turn off the GUI. The server starts in CLI mode, then I launch the GUI using sudo systemctl start display-manager. Personally, I like editing files with a standard text editor and use double command to open needed folders and files. It’s much easier, and double command helps save bookmarks for later.
SSH file transfer offers another method here. With Docker running on the system, installing our app, database, and reverse proxy becomes simply a "docker compose pull && docker compose up" process. Our large cloud servers are managed (like on AWS), so the entire setup is handled through scripts. Typically, there’s no manual work needed on individual machines. An update creates a fresh machine with the latest version, then terminates the old one. From a user perspective, they rarely notice the background change. The whole workflow is fully automated, leaving only the need to tag a new release in GitLab while the build pipeline manages everything else.
SSH Docker works well. I rely on Nginx Proxy Manager to run many sites, some built with Python's SimpleHTTPServer. You can easily get SSL certificates via Let's Encrypt using the `rcp` command over SSH tunnel. Or, you might store files on an SMB share and use File Explorer for uploads.
Completed development of a basic HTML site. File size is minimal yet functional. Seeking contributors to assist in building an open-source file converter for the site.
If you're only using static HTML, GitHub pages can help you collaborate without running other people's code on your system. For server management, I usually install my OS right after connecting to a monitor and then handle it through SSH. Generally, there are two categories of servers: pets and livestock. Pets refer to a small number of systems (one or two) where you handle most configuration manually. Livestock involves many servers that require no individual attention. Pets are managed via SSH, while livestock is handled with automation tools such as Ansible or Chef. You don't need to worry about those tools for just one server. However, when setting up or using your server, you might think how efficiently others do this for thousands of systems. The solution is they automate it at scale.