Selfhosted

50282 readers

259 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

217

I've written a series of blog posts about a "hands-off" self-hosting setup intended for relative beginners. (cyclicircuit.prose.sh)

submitted 1 month ago* (last edited 1 month ago) by cyclicircuit@lemmy.dbzer0.com to c/selfhosted@lemmy.world

43 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] hperrin@lemmy.ca 22 points 1 month ago (16 children)

This is very cool, but also very dangerous. Many projects release versions that need some sort of manual intervention to be updated, and automatically updating to new versions on docker can lead to data loss in those situations.

Here’s a recent example from Immich:

https://github.com/immich-app/immich/releases/tag/v1.133.0

It is my humble opinion that teaching newbies to do automatic updates will cause them to lose data and break things, which will probably sour them from ever self hosting again.

Automatic OS updates are fine, and docker update notifications are fine, but automatic docker updates are just too dangerous.

[–] illusionist@lemmy.zip 3 points 1 month ago (2 children)

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.ca 6 points 1 month ago* (last edited 1 month ago) (1 children)

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.

[–] illusionist@lemmy.zip 3 points 1 month ago

Your probably right, you can't catch each bug I guess

load more comments (13 replies)