this post was submitted on 20 Nov 2025

17 points (100.0% liked)

Selfhosted

selfhosted@lemmy.world

63,723 readers

5,179 active

712 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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 3 years ago

moderators

ruud@lemmy.world

Loki@lemmy.world

CannaVet@lemmy.world

devve@lemmy.world

ayyy@sh.itjust.works

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Making setups resilient to outages (lemmy.zip)

submitted 11 months ago by jobbies@lemmy.zip to c/selfhosted@lemmy.world

8 comments fedilink hide all child comments

Besides "don't use Cloudflare/AWS/etc", how can we make our selfhosted setups resilient to outages like the ones we've seen recently?

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

[–] irmadlad@lemmy.world 3 points 11 months ago

Implement fall backs. If your selfhosted services are public and mission critical, you should have something in your trick bag to fall back to.