Hands-Off Self-Hosting with Docker & Tailscale - an Introduction
cyclicircuit.prose.sh
The first in a series of articles describing an effective self-hosting homelab configuration using docker, Tailscale, and dockge.

Recently, I’ve found myself walking several friends through what is essentially the same basic setup:

  • Install Ubuntu server
  • Install Docker
  • Configure Tailscale
  • Configure Dockge
  • Set up automatic updates on Ubuntu/Apt and Dockge/Docker
  • Self-host a few web apps, some publicly available, some on the Tailnet.

After realizing that this setup is generally pretty good for relative newcomers to self-hosting and is pretty stable (in the sense that it runs for a while and remains up-to-date without much human interference) I decided that I should write a few blog posts about how it works so that other people can set it up for themselves.

As of right now, there’s:

Coming soon:

  • Immich
  • Backups with Syncthing
  • Jellyfin
  • Elementary monitoring with Homepage
  • Cloudflare Tunnels

Constructive feedback is always appreciated.

EDIT: Forgot to mention that I am planning a backups article

  • cyclicircuit@lemmy.dbzer0.comOPEnglish
    8·
    10 days ago

    I don’t disagree with any of that, I’m merely making a different value judgement - namely that a breach that could’ve been prevented by automatic updates is worse than an outage caused by the same.

    I will however make this choice more explicit in the articles and outline the risks.

    • WhyJiffie@sh.itjust.works
      English
      1·
      10 days ago

      with properly limited access the breach is much, much less likely, and an update bringing down an important service at the bad moment does not need to be a thing

    • ikidd@lemmy.worldEnglish
      1·
      9 days ago

      Don’t expose anything outside of the tailnet and 99% of the potential problems are gone. Noobs should not expose services across a firewall. Period.