5 Things I Wish I Knew Before Self Hosting

Brief

A YouTuber reflects on lessons from years of home self-hosting, giving practical advice on hardware, failure planning, networking, containers, and organization — plus a sponsor plug for managed WordPress hosting (Kinsta). Key tech concepts, tools, and recommended practices are summarized below.

Top takeaways (the “5 things” + bonus)

1) You probably don’t need huge hardware

• Most home services (file sync, media servers, home automation, small web apps) are light on CPU and RAM; older low-power machines often suffice.
• Exceptions: heavy real-time video transcoding, large LLMs, or other GPU-heavy tasks.
• Practical rule: start with what you have and upgrade or migrate later if needed.

2) Expect breakage; separate testing and production

• Tinkering will break things — plan for it.
• Maintain separate environments (physical machines or VMs) for testing versus production.
• Use a hypervisor (speaker recommends Proxmox) and keep backups before making changes.
• Know when self-hosting is the wrong choice: critical business sites, essential backups, or when you lack security/networking skills.

3) Learn networking

• Core topics to understand: IPs/subnets, DNS, and routing.
• Use learning resources such as Linux Journey’s networking section.
• Implement VLANs early to isolate untrusted devices and better organize networks.
• Avoid opening firewall ports directly; prefer VPNs (WireGuard) or Cloudflare Tunnels for remote access.

4) Learn Docker (and container orchestration)

• Benefits: lightweight isolation vs VMs, portability (image + config + data), and easier migration.
• Use Docker Compose (or an equivalent) instead of ad-hoc docker run commands to keep configurations reproducible.
• Portainer (used by the speaker) provides a GUI and supports Compose-style stacks for management.

5) Stay organized and document everything

• Keep deployment notes, config files, network diagrams, repository access, and migration instructions documented.
• For larger setups, use wikis and infra-as-code so deployments are reproducible (examples: Ansible, NixOS — note: NixOS was imperfectly spelled in the transcript).
• Anecdote: an undocumented Slackbot deployed on an old Mac Mini became a multi-year headache to migrate.

Bonus: There are no single “right answers”

Many valid ways exist to solve problems — pick what fits your use case and available time. Try new tools to learn, otherwise stick with what reliably works.

Tools & services referenced

• Proxmox (hypervisor)
• Docker, Docker Compose, Portainer (containers / orchestration / management)
• VLANs (network segmentation)
• WireGuard, Cloudflare Tunnels (secure remote access)
• Linux Journey (networking learning resource)
• Jellyfin (media server example)
• WordPress (example of hosting needs)
• Ansible / NixOS (infra-as-code options)

Sponsor — Kinsta (managed WordPress hosting)

• Dashboard for sites, databases, and apps; migrations included.
• Security: enterprise firewalls, DDoS protection, containerized architecture, SOC2 compliance.
• SLA: 99.99% uptime guarantee; human support (not “AI only”).
• Performance features: edge caching, early hints, 37 data centers, 300+ CDN locations, claims of substantial speed improvements.
• Offer: first month free plus a 30-day money-back guarantee (via link/QR in the original video).

Guides & tutorials mentioned or implied

• Creator’s channel videos on using older low-power hardware and self-hosting examples.
• Docker tutorials and Compose/Portainer guides.
• Linux Journey networking section.
• Jellyfin tutorials (example for replacing subscription services).

Main speakers / sources

• The video’s narrator / YouTuber (author of the self-hosting tips)
• Kinsta (sponsor)
• Linux Journey (recommended learning resource)