Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
view the rest of the comments
I have used (and loved) Yunohost for a long time, and I host it at home. A few years back, I did set up a vps to proxy the traffic (over wireguard) so that I could actually get a letsencrypt cert. Some apps really don't like self-signed certs.
You do not need a VPS, proxy, or wireguard for letsencrypt.
Right? This is the whole "lack of understanding" that I'm going on about. "But the install instructions for some other application said to do this." So it becomes cargo-cult system administration.
It's how we end up with
curl https://some.rando.url/install.sh | sudo bash -cas an acceptable way of installing software. Don't understand it, don't question it, don't look at what that shell script you're running as root does, just copy / paste / and go! I don't want to care about the details!And you see it in the comments in this forum where anytime anyone asks a question there are dozens of replies like "just use yunohost" or "just rebuild your entire server with unraid" without addressing the one component that needs addressing or offering multiple solutions. It's just "my click and forget solution worked for me so it's the way everyone should do it."
This is how we end up with walled gardens - to protect these people from themselves. Self-hosting should involve some amount of learning about what you're doing because "there be dragons" out there.
I have nothing against yunohost or letsencrypt (the latter is simply amazing) - but one should understand that these things are components that are part of a larger system.
I absolutely feel your pain. However, there is also the side that all this complexity must be handled somehow. The other extreme is that you'd have to compile all the software and its dependencies from scratch, as well as read and understand the source code.
In the end, it boils down to the people who actually care (like you, who is probably one of them) to exercise caution—looking at the output of
curl https://some.rando.url/install.shbefore doing the| sudo bash -cand constantly insisting on the validity and absolute necessity of signature checks, transparency, and so on. Meanwhile, all the other folks get at least a foothold in self-sovereignty without being completely smashed by the details of compiler flags.