My Linux server or my Widows server in the ever-evolving world of technology, having control over your own server is like owning a piece of digital real estate. For me, that piece is a Linux server—a humble yet powerful machine that handles everything from hosting websites to serving as a remote development environment. This article is a behind-the-scenes look at how My Linux server or my Widows server operates, what I use it for, and why I chose Linux over other operating systems like Windows.
My Linux Server or My Widows Server? A Step-by-Step Guide
Why I Chose Linux
My journey into self-hosting began a few years ago. I wanted to learn more about backend systems, web hosting, and server security. While cloud solutions like AWS or DigitalOcean were tempting, I felt a pull toward building something I could control completely. That meant getting physical hardware—or at least a VPS—and installing my own operating system.
Linux stood out for a few key reasons:
- Open-source and free: No licensing costs.
- Highly customizable: I could trim the fat and run exactly what I needed.
- Community support: Endless resources, forums, and documentation.
- Stability: Linux rarely crashes and can run for months—even years—without rebooting.
I opted for Ubuntu Server LTS—a long-term support release that balances stability with access to updated packages.
The Hardware
My setup is modest but effective:
- CPU: Intel Core i5
- RAM: 16 GB DDR4
- Storage: 1 TB SSD + 2 TB HDD
- Network: Gigabit Ethernet
The SSD holds the operating system and critical applications, while the HDD stores backups and media files. I repurposed an old desktop, installed Ubuntu Server via USB, and got it running headless (no monitor needed, all SSH access).
For remote access, I use SSH with key-based authentication. No password logins—security first.
Services Running on My Linux Server
- Web Hosting (Nginx + PHP + MySQL)
I host several websites and personal projects using the LEMP stack (Linux, Nginx, MySQL, PHP). Nginx is leaner & faster than Apache, especially under load. I’ve also set up SSL certificates via Let’s Encrypt to ensure HTTPS for all my domains.
Each site runs in its own directory, and I use virtual hosts to direct traffic. This allows me to keep projects organized and isolate issues if something breaks. - Docker for Containers
Rather than installing every tool or service directly on the OS, I use Docker to containerize many apps. This includes:- A self-hosted Git server
- Nextcloud for file syncing
- A personal wiki (via Wiki.js)
- PostgreSQL and Redis containers for development
Docker makes version management easier and lets me spin up or remove apps without polluting the base system.
- Home Media Server
Using Plex & Samba, my Linux server doubles as a home media center. I’ve ripped my DVD collection, stored family photos, and even recorded TV streams. Plex allows me to stream content to any device in the house—or remotely—complete with metadata and subtitles. - Development Environment
I use my server as a remote dev box. With tools like VS Code Remote SSH, I can code directly on the server from my laptop. This allows for testing in a real Linux environment with all dependencies installed.
I also use tmux and vim when I want to keep things lightweight and terminal-based. It’s fast, efficient, and perfect for SSH work on the go. - Backups and Syncing
Data loss is one of my worst fears, so I use rsync to back up my critical files daily to an external drive. I also use BorgBackup for compressed and encrypted backups to a remote cloud server.
In addition, I have Nextcloud installed to sync my devices and keep documents backed up across multiple platforms.
Security Measures
Running a public-facing server means taking security seriously. Some of the steps I’ve taken include:
- SSH keys only (no password logins)
- Fail2ban to block brute-force attempts
- UFW (Uncomplicated Firewall) to restrict traffic
- Auto-updates for security patches
- Regular audits with tools like Lynis and chkrootkit
I also monitor my logs regularly with Logwatch, and keep a close eye on system resource usage using htop and netstat.
Maintenance and Monitoring
My Linux server is low maintenance, but I do have a routine:
- Weekly updates with apt update && apt upgrade
- Docker image and container cleanups
- Monthly reboot (just to apply kernel updates)
- Daily backups and integrity checks
For monitoring, I use Netdata and Grafana. They provide real-time stats on CPU usage, RAM, disk I/O, and network traffic—helpful for spotting issues before they become problems.
Lessons Learned
Running a Linux server has taught me more than I expected. From networking to scripting, file permissions to cron jobs, every issue has been a learning opportunity.
Some lessons include:
- Always have a backup before upgrading anything.
- Keep logs—don’t delete them until you’re sure you won’t need them.
- Simplicity is better than complexity. Don’t install 20 apps when 3 will do.
- Use version control even for config files—tools like etckeeper help.
Conclusion
My Linux server or my Widows server is more than just a machine—it’s a platform for learning, creating, and controlling my digital presence. Whether I’m developing a new app, hosting a site, or streaming a movie, I know exactly what’s going on under the hood.
Linux has given me the power and freedom to build and manage my own infrastructure. It’s not always easy, and there are challenges along the way, but the reward is worth it: complete control, deep technical understanding, and the satisfaction of self-reliance.
If you’re thinking about setting up your own My Linux server or my Widows server, I say go for it. Start small, break things, learn fast—and remember: Google and Stack Overflow are your best friends.
