Wong Edan's
Cover
DevOps & Infrastructure

Escape the Cloud: The Ultimate Guide to Digital Sanity

March 08, 2026 • By Azzar Budiyanto

Welcome to the Asylum: Why Self-Hosting is the Only Sane Choice

Greetings, fellow digital wanderers and data-hoarding lunatics. If you have found yourself browsing the r/selfhosted subreddit at three in the morning, wondering why you are paying Google, Dropbox, and Netflix for the privilege of spying on you, then you have come to the right place. They call us “Wong Edan”—the crazy ones. But let me ask you this: Is it crazy to want to own your own photos? Is it “edan” to prefer your documents stay on a hard drive in your closet rather than a server farm in Virginia owned by a billionaire who thinks privacy is a legacy bug?

Self-hosting is the art of reclaiming your digital sovereignty. It is the process of running your own services—email, file storage, media streaming, home automation—on your own hardware. It is a journey filled with triumph, sudo commands, and the occasional 2:00 AM existential crisis when your reverse proxy decides to stop serving SSL certificates. This guide is for the “idiot” in all of us—the person who knows that “The Cloud” is just someone else’s computer and wants to take their computer back.

Phase 1: The Hardware (Don’t Buy a Rack… Yet)

The biggest mistake beginners make is thinking they need a 42U server rack and a noise-canceling basement to start. You don’t. In fact, if you start too big, you will burn out faster than a cheap SSD. The beauty of self-hosting is that it can run on almost anything that has a pulse (and an Ethernet port).

The “Dusty Laptop” Method

Do you have a laptop from 2018 with a cracked screen and a battery that lasts twelve minutes? Congratulations, you have a server. Laptops are actually incredible for beginners because they have a built-in Uninterruptible Power Supply (the battery) and a built-in KVM (the keyboard and screen). Just wipe that bloated Windows 10 install and you are ready to rock.

The Mini PC Revolution

If you have a few hundred dollars to spare, look into the N100 or N5105 Mini PCs. These tiny boxes consume about as much power as a lightbulb but are powerful enough to run dozens of containers. Brands like Beelink or Minisforum are the darlings of r/selfhosted for a reason. They are silent, small, and won’t make your electricity bill look like a phone number.

The Raspberry Pi (If You Can Find One)

The Raspberry Pi 4 or 5 is the classic entry point. It is great for learning, but be warned: SD cards are the devil. If you go the Pi route, boot from an external SSD. Nothing kills the “Wong Edan” joy faster than a corrupted SD card taking down your entire smart home while you’re trying to turn on the lights.

Phase 2: The Operating System (Choose Your Fighter)

Repeat after me: Linux is my friend. While you can host on Windows, doing so is like trying to run a marathon in a tuxedo. It’s heavy, it’s awkward, and it will eventually force a reboot for updates right when you’re in the middle of a movie.

Debian vs. Ubuntu

For a “complete idiot’s guide,” I recommend Ubuntu Server or Debian.

  • Ubuntu Server: It’s the “it just works” option. Most tutorials online are written for Ubuntu. It has great driver support and a massive community.
  • Debian: It is the rock-solid grandfather of Ubuntu. It is leaner and “purer.” If you want your server to stay up for three years without a hiccup, Debian is the way.

One critical tip from the Reddit hivemind: Do not install the Desktop version. You don’t need a GUI (Graphical User Interface). A GUI wastes RAM and CPU cycles. You will learn to love the Terminal. The Terminal is where the magic happens. It is where you feel like Neo in The Matrix, even if you are just typing sudo apt update.

Phase 3: The Holy Grail – Docker and Docker Compose

If there is one thing you take away from this guide, let it be this: Docker is not optional. In the old days, if you wanted to install a media server, you’d install it directly on your OS. It would change your system libraries, leave trash everywhere, and if you wanted to uninstall it, it would leave “ghost” files behind. Docker changes everything.

What is Docker?

Imagine a shipping container. Inside that container is everything an app needs to run—the code, the libraries, the settings. You just drop that container onto your server, and it works. It doesn’t touch your main system. If you don’t like it, you delete the container, and your server is as clean as the day you installed it.

Docker Compose: The Recipe Book

Docker Compose allows you to write a simple text file (a .yaml file) that describes your entire setup. Here is what a simple “Hello World” style setup for a dashboard might look like:


services:
  homepage:
    image: ghcr.io/gethomepage/homepage:latest
    container_name: homepage
    ports:
      - 3000:3000
    volumes:
      - ./config:/app/config
    restart: unless-stopped

You save that file, run docker-compose up -d, and boom—you’re hosting. It’s that simple. No more dependency hell. No more “it works on my machine” excuses.

Phase 4: Networking – Opening the Gates (Carefully)

So, you have an app running on your server. It’s at 192.168.1.50:3000. But you’re at a coffee shop and you want to see your dashboard. This is where beginners usually get hacked because they do something “edan” like opening every port on their router.

The Reverse Proxy: Nginx Proxy Manager (NPM)

As mentioned in the Reddit threads, Nginx Proxy Manager is the “idiot-proof” way to handle incoming traffic. Instead of opening port 3000 for your dashboard, port 8080 for your photos, and port 9000 for your music, you only open ports 80 (HTTP) and 443 (HTTPS).

NPM acts as the traffic cop. When you go to dashboard.yourdomain.com, NPM looks at the request and says, “Ah, you want to go to the dashboard container! Let me pass you through.” It also handles your SSL certificates via Let’s Encrypt, so you get that sweet, sweet green padlock in your browser for free.

Static IPs and DNS

Your home internet IP address likely changes every time your router reboots. To fix this, you need a Dynamic DNS (DDNS). Services like DuckDNS, Cloudflare, or No-IP give you a domain name that always points to your home, no matter how often your IP changes.

“A man who does not secure his ports is a man who invites the world to delete his databases.” — An ancient self-hosting proverb I just made up.

Phase 5: Security – Don’t Be a Statistic

The internet is a scary place. Within five minutes of putting a server online, bots from all over the world will start knocking on your door. If you use a password like “password123,” you are doomed.

The VPN Strategy (Tailscale/WireGuard)

The “safest” way to self-host is to not open any ports at all. How? Use a VPN. Tailscale is the current king of the r/selfhosted community. It uses the WireGuard protocol to create a private network between your devices. Your server thinks your phone is in the next room, even if you are halfway across the globe. No ports opened, no hackers allowed.

Two-Factor Authentication (2FA)

If you must expose a service to the internet (like a photography portfolio for clients), you need 2FA. Use something like Authelia or Authentik. These sit in front of your apps and demand a code from your phone before letting anyone in. It’s the digital equivalent of a bouncer with a very bad attitude.

Phase 6: The “Killer Apps” – What to Host First?

Now that the foundation is laid, what do you actually do with this digital beast? Here are the gateway drugs of self-hosting:

  • Nextcloud: The ultimate Google Drive/Photos replacement. It does files, calendars, contacts, and even has a built-in office suite. It’s heavy, but it’s powerful.
  • Pi-hole or AdGuard Home: These act as a DNS sinkhole. They sit on your network and gobble up every advertisement and tracker before they even reach your computer or phone. It’s like an ad-blocker for your entire house.
  • Jellyfin: Like Netflix, but you own the movies. It’s open-source and doesn’t charge you for “premium” features like Plex does.
  • Immich: A high-performance self-hosted photo and video management solution. It’s currently the best alternative to Google Photos, featuring AI face recognition and a beautiful mobile app.
  • PigeonPod: A niche but cool app mentioned in the Reddit weekly spotlights. It converts YouTube channels into podcast feeds. Perfect for listening to video essays while you drive without burning your data plan.

Phase 7: The “Sometimes I Hate Self-Hosting” Reality Check

Look, I’m a tech blogger with a “Wong Edan” personality, so I have to be honest with you. Self-hosting isn’t always sunshine and low latency. There will be days when your Traefik instance stops serving certificates for no reason. There will be days when a Docker update breaks your database mapping.

The 3-2-1 Backup Rule

If you don’t have backups, you don’t own your data; you’re just borrowing it from fate. Follow the 3-2-1 rule:

  1. Keep 3 copies of your data.
  2. Store them on 2 different types of media (e.g., an internal drive and an external USB).
  3. Keep 1 copy offsite (e.g., encrypted on Backblaze B2 or at your mom’s house).

Monitoring and Maintenance

Use an app like Uptime Kuma. It will send you a notification on Telegram or Discord when one of your services goes down. It is much better to find out your server crashed at 10 AM while you’re at work than at 8 PM when you’re trying to watch a movie with your spouse and the “smart” TV won’t connect.

Phase 8: Dive into the Community

You are not alone in your madness. The r/selfhosted community is one of the most helpful places on the internet, provided you’ve at least tried to read the documentation first. Before you post a question, search the sub. Chances are, someone else has already had their heart broken by the same configuration error you’re currently facing.

Read the Self-Host Weekly newsletters. Keep an eye on new projects like Ente (for encrypted photo storage) or Uptime Kuma (for monitoring). The landscape changes fast, and that’s part of the fun.

Conclusion: The Path of the Digital Sovereign

Self-hosting is a journey, not a destination. You will start with a single Pi-hole and before you know it, you’ll be debating the merits of ZFS over BTRFS and calculating the IOPS of your NVMe array. You’ll become the “Wong Edan” of your friend group—the one who doesn’t use Gmail and hosts their own encrypted chat server.

Is it hard? Sometimes. Is it worth it? Absolutely. There is a profound sense of satisfaction that comes from knowing that your data is yours, your privacy is intact, and you are no longer a product being sold to the highest bidder. So, grab that old laptop, install Debian, and welcome to the asylum. We’ve been waiting for you.

Now go forth and sudo!