{"id":1063,"date":"2026-08-25T22:39:47","date_gmt":"2026-08-25T22:39:47","guid":{"rendered":"https:\/\/affordablevpsserver.com\/blog\/?p=1063"},"modified":"2026-10-08T22:02:28","modified_gmt":"2026-10-08T22:02:28","slug":"linux-learning-lab-budget-vps-starter-guide","status":"publish","type":"post","link":"https:\/\/affordablevpsserver.com\/blog\/linux-learning-lab-budget-vps-starter-guide\/","title":{"rendered":"Linux Lab on a $5 VPS: Commands, Projects, and a 30-Day Roadmap"},"content":{"rendered":"\n

A $5\/month VPS is the cheapest way to own a real Linux server that runs 24\/7 with a public IP. Unlike a local virtual machine, everything you break is real: networking, firewall rules, SSH keys, and disk layout. This walkthrough covers the commands and projects that turn a cheap VPS into a working lab for Linux, networking, and DevOps skills \u2014 without a paid course.<\/p>\n\n\n\n

First 15 Minutes: Secure the Server<\/h2>\n\n\n\n

On first login you have an IP and a root password. Lock it down before anything else:<\/p>\n\n\n\n

# Update everything\napt update && apt upgrade -y\n\n# Create a regular user\nadduser lab\nusermod -aG sudo lab\n\n# Copy your SSH key up (from your laptop)\nssh-copy-id lab@your-server-ip\n\n# Disable password login for root\nsed -i 's\/^#PermitRootLogin.*\/PermitRootLogin no\/' \/etc\/ssh\/sshd_config\nsed -i 's\/^#PasswordAuthentication.*\/PasswordAuthentication no\/' \/etc\/ssh\/sshd_config\nsystemctl restart ssh<\/code><\/pre>\n\n\n\n
Add a firewall rule set next. ufw allow 22<\/code>, then ufw allow 80<\/code> and 443<\/code>, then ufw enable<\/code>. Install fail2ban<\/code> to auto-block brute-force attempts \u2014 on a public IP these start within hours.<\/p>\n\n\n\n
The Core Command Set to Master<\/h2>\n\n\n\n
Task<\/th>Command<\/th><\/tr><\/thead>
Disk usage by directory<\/td>du -sh \/* | sort -h<\/code><\/td><\/tr>
Live resource view<\/td>htop<\/code><\/td><\/tr>
Open listening ports<\/td>ss -tulpn<\/code><\/td><\/tr>
Follow a live log<\/td>journalctl -fu nginx<\/code><\/td><\/tr>
Service control<\/td>systemctl status|restart|enable<\/code><\/td><\/tr>
Find large files<\/td>find \/ -type f -size +100M<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Memorize systemctl<\/code> and journalctl<\/code> first. Almost every service you install \u2014 web server, database, VPN \u2014 is managed the same way, so learning the pattern once pays off across all of them.<\/p>\n\n\n\n
Projects That Build Real Skills<\/h2>\n\n\n\n
Run these in order. Each one introduces a layer of the stack that employers and real deployments depend on:<\/p>\n\n\n\n
    \n
  1. Static site with NGINX<\/strong> \u2014 serve a folder over HTTP, then add TLS with a free Let’s Encrypt certificate via certbot<\/code>. This teaches DNS, ports, and TLS end to end.<\/li>\n\n\n\n
  2. Reverse proxy<\/strong> \u2014 run a small app on port 3000 and proxy it through NGINX on 443. This is the pattern behind nearly every production deployment.<\/li>\n\n\n\n
  3. Database<\/strong> \u2014 install PostgreSQL or MariaDB, create a user, and connect from the app. Practice backing it up with pg_dump<\/code>.<\/li>\n\n\n\n
  4. Containerize<\/strong> \u2014 install Docker, run the same app in a container, and mount a volume for persistence. Compare the memory footprint of container vs native install.<\/li>\n\n\n\n
  5. Automation<\/strong> \u2014 write a cron job that backs up a database nightly and rotates old copies.<\/li>\n<\/ol>\n\n\n\n
    When you are ready to size a server that can run several of these at once, the budget VPS specifications listed at affordablevpsserver.com<\/a> show what each RAM tier realistically supports, so you can grow the lab without paying for headroom you do not need yet.<\/p>\n\n\n\n
    Monitoring Your Lab for Free<\/h2>\n\n\n\n
    You cannot learn operations without watching a system under load. Install these at no cost:<\/p>\n\n\n\n