this post was submitted on 01 Mar 2026
297 points (96.8% liked)

Selfhosted

57155 readers
1125 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] corsicanguppy@lemmy.ca 7 points 3 days ago* (last edited 3 days ago)

What's the big deal? For 20 years in the enterprise space it's been yum upgrade -y && reboot into cron and no issues. At the day job I even had satellite (5 and that shitball 6) cronned up to do my promotion automatically (even when 6 had shit for scheduling and I had to cron-parallel-xargs a better one). All cron.

Hell, I barely pay attention to the email reports now. It's been that long. Okay, prod updates on Friday night only; but that's our only nod to risk. Because even after the metastatic fatberg that is Systemd, it's still barely reliable.

What's the added risk for Debian packages? Imperfect replacement? No signed manifest to compare against? What?