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

  • illusionist@lemmy.zipEnglish
    3·
    1 day ago

    Immich is still unstable. This shouldn’t happen to a stable project.

    What it tells me is that you need a regular backup

    • hperrin@lemmy.caEnglish
      6·
      1 day ago

      This absolutely can happen to stable projects. This has happened with Mastodon many times, and Mastodon has been stable for years.

      It also has happened with Nextcloud many times, and again, Nextcloud has been stable for years.

      It’s not a stability thing, it’s an automation thing. We as devs can only automate so much. At a certain point, it becomes up to you, as the administrator, to manually change things. Things like infrastructure changes, and database migrations, where the potential downtime if we automate it is something we need to consider.