this post was submitted on 17 Feb 2026
105 points (94.1% liked)

Selfhosted

56703 readers
455 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
 

The fourth article in my series about "self-hosting for newbies" explaining how I take care of backups for my YunoHost server.

you are viewing a single comment's thread
view the rest of the comments
[–] rimu@piefed.social 10 points 3 days ago (21 children)

No, it's legit. Elena has been tooting and peertubing about the fedi and her self hosting journey for over a year.

[–] atzanteol@sh.itjust.works 3 points 3 days ago (20 children)

It still reads like an ad for yunohost...

I think one of the mistakes many newb self hosters make is thinking of systems in their entirety rather than as components.

"How to install pihole on a raspberry pi" and "how to setup nextcloud on yunohost" are examples. All using very specific tools and very specific steps.

I'm noticing this more and more with documentation for apps where they tell me to use their specific docker-compose file and have instructions to use let's encrypt in a specific way rather than referring you to let's encrypt as an option and pointing you at their docs.

People aren't learning how to use each of these tools and how to be flexible in their implementation.

[–] kossa@feddit.org 11 points 3 days ago (2 children)

Depends highly on the people. I learned that way, to get started with recipes enabled me to get early successes which in turn motivated me.

Down the road I needed different things from my setup, which could not be found in a simple recipe anymore, so I needed to learn the parts of the machine.

[–] tedd_deireadh@piefed.social 7 points 3 days ago (1 children)

Exactly. Both newbies and experienced admins aren't always looking for a general summary on how to build something. Sometimes we need a direct, easy guide to build the tool we've already decided to implement. Let them read the documentation so I don't have to.

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

Let them read the documentation so I don't have to.

Exactly why the article promotes stupidity. Why in the world would you put those words down proudly?

load more comments (17 replies)
load more comments (17 replies)