The switch to Linux and the beginning of my self-hosting journey

Original Article ↗ Hacker News Discussion ↗

Self‑hosting: pain, fun, and tradeoffs

  • Strong disagreement on “self‑hosting sucks”: some find it a frustrating time sink, others see it as a deeply rewarding hobby and learning experience.
  • Consensus that it’s not for everyone, and especially not for non‑technical family members who just want reliability.
  • Biggest problems cited: ongoing maintenance, breakage after updates, security exposure of internet‑facing services, backups, and being the unpaid sysadmin for friends/family.
  • Several say it’s “less painful than it used to be” thanks to modern apps (e.g., Immich), containers, VPN tools like Tailscale, and LLMs for troubleshooting.

Architectures, tools, and security

  • Many recommend starting simple: one Linux box with Docker/docker‑compose, using web UIs (e.g., Dockge) instead of full hypervisor stacks.
  • Proxmox is seen as powerful but overkill/confusing for beginners; others argue it’s approachable and great for GPU passthrough and easy OS re‑installs.
  • KVM/virt‑manager gets mixed reviews: powerful but confusing UI and permission pitfalls.
  • Networking pain points: TLS, reverse proxies, DNS, port forwarding. Several advocate “VPN first” (WireGuard/Tailscale/Cloudflare tunnels) and keeping everything off the public internet.
  • DDNS + exposed services are criticized as high‑risk; suggestion is VLANs, VPN‑only access, and reverse proxies for any public exposure.

Linux desktop vs Windows

  • Many praise Linux for being quiet, ad‑free, and not interrupting work/games with forced updates, in contrast to Windows 10/11 notifications, ads, and “AI” UI clutter.
  • Others push back: some Windows setups show very few notifications; experiences vary by edition and installed software.

Usability, distros, and package management

  • One tester of CachyOS/Aurora concludes “Linux still isn’t there” after struggling to install JetBrains IDE from a tarball in a live session; they reject any need for terminal usage.
  • Multiple replies argue this is misuse: on Linux you’re expected to use package managers (GUI or CLI) instead of vendor tarballs; CachyOS and others ship GUI stores (Discover, Software, Snap Store, etc.).
  • General advice: avoid niche/over‑customized distros when evaluating Linux; start with mainstream options (Mint, Ubuntu flavors, Fedora, openSUSE) and familiar desktops (KDE, Cinnamon, GNOME).

Debian vs Fedora vs “latest kernels”

  • Debate over Debian “stable”: critics say it’s too old for modern GPUs and drivers; defenders note current releases and backports/testing/unstable as options.
  • Fedora and Arch‑like systems are praised for up‑to‑date kernels and fewer hardware quirks; others prefer LTS stability and fewer surprise regressions.

Wayland and graphics

  • Wayland is a flashpoint: some report improved performance and consider it “solved,” others encounter broken input handling, drag‑and‑drop issues, Steam/Proton crashes, accessibility gaps, and kernel instability.
  • X11 users (e.g., on Mint) are wary of the transition; workarounds like XWayland or forcing X sessions are common.

Drivers, Nvidia, and hardware selection

  • A fresh Nvidia driver update that drops a system into BusyBox is given as an example of why some avoid Linux on the desktop.
  • Explanation: out‑of‑tree Nvidia modules + DKMS can fail on kernel changes; rolling back to an older kernel is a typical fix.
  • Several note that Linux desktop reliability improves dramatically when hardware is chosen with Linux support in mind or bought from Linux‑focused vendors.

Meta: why this post and hardware choices for homelabs

  • Some question the novelty of the original blog; others value beginner journey write‑ups as motivation and discussion starters.
  • Debate over Raspberry Pi vs used mini‑PCs: Pis seen as overpriced and less robust for self‑hosting compared to cheap second‑hand x86 boxes.