this post was submitted on 29 Oct 2025
90 points (98.9% liked)

Selfhosted

52632 readers
769 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.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Or asked the other way around: How long do you keep your servers running without installing any software updates?

update means something like

sudo dnf update

or something ....

apt-get upgrade
apt-get update
(page 2) 20 comments
sorted by: hot top controversial new old
[–] snekerpimp@lemmy.world 2 points 2 days ago

Almost everything I have runs Debian or NixOS, so…….. once a month? Except for VMs I’m playing around with, which usually get updated every time I log into them, or instal stuff.

[–] eager_eagle@lemmy.world 2 points 2 days ago* (last edited 2 days ago)

everyday to once a month, depending how often I use the server

IME usually waiting longer to apply larger updates causes more issues than smaller and more frequent ones

[–] BCsven@lemmy.ca 1 points 2 days ago

Depends, on how critical something is...since we deal with servers / customers at work that often are purposely not adjusted for years...because introducing a different behaviour (even if better) would grind production to a halt, I take a not careful approach.

I was using OpenSUSE Leap, and with zypper you can review which patches are available, whether they are critical or run recommended or not needed. You can then apply which specific patch you want be CVE if necessary.

But with Leap's path seaming messy at the moment, I moved to Tumbleweed, since you have snapshotying built in. If an update did mess something up you just rollback to the previous snapshot and in less than a minute it is fixed

[–] MTK@lemmy.world 1 points 2 days ago

Anything exposed to the internet gets a daily / weekly update, depending on how exposed it is, how stable the updates are and how critical a breach would be. For example nginx would be a daily update.

Anything behind a vpn gets a more random update schedule mostly based on when I feel like it (probably around once a month or every other month)

[–] atzanteol@sh.itjust.works 1 points 2 days ago

All systems, daily via a single ansible script. That's apt update, upgrade and reboot if needed (some systems set to only reboot with a separate script so I can handle them separately).

Rarely have any sort of problems.

[–] Luckyfriend222@lemmy.world 1 points 2 days ago

First Friday of the month. Easy to remember.

[–] 30p87@feddit.org 1 points 2 days ago

Every day to once a week, depending on free time

[–] ilco@feddit.nl 1 points 2 days ago

Usely every 3/4 months roughly. I try to remeber to update. The base. Server. And docker based things! /webserices. I update. Sparingly. Every few new versions. As I am the only user of my server. I don't have a high need to update. So I update only if a new future. Is added or a mayor bug /security patch.

[–] corsicanguppy@lemmy.ca 0 points 1 day ago

Yum-cron. Daily. Rolling bounce on a schedule.

It has been rock-solid for 20 years, but lennart's cancer and the growing amount of shite they're shoveling into EL has caused a few issues here and there with 7, 9 and 10. (Skipped 8 because f that)

But, today, it works. So that's year 23 and 8 months.

load more comments
view more: ‹ prev next ›