this post was submitted on 20 Sep 2023
39 points (93.3% liked)

Fediverse

28422 readers
941 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
 

I am honestly kinda curious how exactly you manage your servers and keep them up to date, I feel like there is a linux patch every week or so, which would usually require a reboot. Do you all deploy live patching, how you become aware of critical stuff in your otherwise busy lives, RSS?

you are viewing a single comment's thread
view the rest of the comments
[–] thisisawayoflife@lemmy.world 3 points 1 year ago (1 children)

Perform automatic updates and reboot when necessary.

If one is serious about hosting this, it's best to isolate the services. One container or VM or reach service, with (probably) physical hosts for the DBs.

Schema change is more involved, but backup then update. If you have read only db, it should sync the changes when reconnected.

Realistically, federated data will be re-sent if the recipient doesn't respond, so a few minutes of downtime is not the end of the world. At least that's how mastodon works - not sure about Lemmy but I'm presuming it operates in a similar fashion.

[–] skymtf@lemmy.blahaj.zone 1 points 1 year ago (1 children)

Couldn't auto updates break things if they arnt tested?

[–] thisisawayoflife@lemmy.world 3 points 1 year ago

They should be tested upstream of you, assuming you aren't using customized (eg roll your own) versions of any of the ancillary software (php, pgsql, redis, etc). Generally configs are either merged or not adopted, and you can restrict version upgrades to non major releases, if there's chances of breakages between them (eg moving from pgsql 9 to 10, etc).