What I Self-Host
- ID
- 36144
- Status
- summarized
- Published
- 16 Oct 2026, 4:23 AM
- Fetched
- 16 Oct 2026, 10:16 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://viceconsole.fyi/blog/2026/10/10/what-i-self-host/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.0
- Created
- 16 Oct 2026, 10:16 AM
- Tags
- Audience
- developersvibe_coders
What happened
A self-hosting write-up describing how the author replaced Netflix, Disney+ and Spotify with self-hosted Jellyfin, then expanded to running many other services at home over roughly 18 months. The concrete rules: no service is exposed directly to the public internet except VPN servers running on the router, the ISP uses CGNAT for IPv4 so the home network isn't publicly reachable, and the VPN is therefore only routable over IPv6 — which breaks it on most public Wi-Fi. The author prefers native installs over containers, loves single Go binaries, and skips any service that ships only as a Docker Compose file pulling in MySQL, Redis and three more containers.
Why it matters
This is a real cost-and-control decision, not a hobby flex: the author dropped western streaming prices and the 'recommended for you' autoplay loop, and pays for it with an IPv6-only remote-access setup. If you run anything at home on a consumer fibre plan that hands out CGNAT IPv4 — common in Malaysia and much of SEA — you will hit the exact same wall, and the workaround here (VPN on IPv6, no inbound IPv4) is the pattern to copy or reject before you buy hardware. The dependency rule is the other decision: 'single Go binary' as the bar, and Docker Compose stacks with MySQL plus Redis as a disqualifier, is a usable filter when picking what to actually run.
Discussion angle
Where do you draw the native-vs-container line, and what's your remote-access plan if your ISP gives you CGNAT IPv4 and an IPv6-only path — does that change which services you're willing to host at all?