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'd you're going to self host you need to learn. I have no time for kids who just want "Google but free" and don't want to spend any time learning what it takes to make that happen.
we shouldn't need to pay for a domain to be able to self host.
You don't need to if you're just using things locally.
But also - domains are cheap.
yes you need if you want HTTPS that is accepted by the smartphone client apps of your services.
domains are a constant expense
They're cheap. You can also generate your own certs and use your own ca. But otherwise yes - quit yer bitching and learn how to do things right.
I do this, with a custom root cert, but it has problems. some apps don't accept it, some only accept it by totally disabling cert verification.
installation is also very cumbersome: you go to a weird, badly structured menu on your phone deep in the settings, and select the certificate from storage where apps could have had replaced it while you were navigating the menu.
it does not ask you for confirmation, does not show anything important about the cert, like its fingerprint you could use to quickly check its not been modified, any name constraints, validity period, etc. users cannot tell what that cert will grant its creator, because the system does not tell them anything so that they could decide, other than a generic "your connection may be monitored" message at all times. and when they refuse to install your cert, they are right, because this way it is very risky.
so please tell me "how to do things right", or shut up if you can't tell any useful info