cyclicircuit

joined 1 year ago

I am very happy to hear that. Sadly I don't know what to do about the images not loading. I am just using the free tier of pico.sh, so I imagine that corners have been cut for pathological consumers like me. If you ever need a specific image or something doesn't make sense, feel free to DM!

[–] cyclicircuit@lemmy.dbzer0.com 1 points 2 months ago (1 children)

Its covered in the introduction what's expected of the reader and server setup, and towards the end of the intro I go over the unattended-upgrades setup.

[–] cyclicircuit@lemmy.dbzer0.com 4 points 2 months ago

Yeah a little xD but FWIW this article series is based on what I personally run (and have set up for several friends) and its been doing pretty well for at least a year.

But I have backups which can be used to recover from the issues with breaking updates.

[–] cyclicircuit@lemmy.dbzer0.com 1 points 2 months ago

Yeah I agree with the warnings. One of the things I'm trying to ensure I get across accurately (which will be discussed later in the series) is how to do monitoring. Making sure backups are functioning properly would need to be a part of that.

[–] cyclicircuit@lemmy.dbzer0.com 8 points 2 months ago (2 children)

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.

[–] cyclicircuit@lemmy.dbzer0.com 5 points 2 months ago

Hmmmm that's a good point. I'll try to work. that in P: cause Tailscale can cause issues if you're already doing Wireguard or something.

[–] cyclicircuit@lemmy.dbzer0.com 1 points 2 months ago

Sweet! Thank you! I'll test it out and update the blog posts to reflect that

[–] cyclicircuit@lemmy.dbzer0.com 10 points 2 months ago (3 children)

Naturally, the same day that I publish this, I discover that Watchtower is semi-abandoned, so I'm gonna have to look into alternatives to that...

[–] cyclicircuit@lemmy.dbzer0.com 9 points 2 months ago (11 children)

That's reasonable, however, my personal bias is towards security and I feel like if I don't push people towards automated updates, they will leave vulnerable, un-updated containers exposed to the web. I think a better approach would be to push for backups with versioning. I forgot to add that I am planning a "backups with Syncthing" article as well, I will take this into consideration, add it to the article, and use it as a way to demonstrate recovery in the event of such an issue.

 

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