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.
Resources:
- 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
While I like it conceptually, the two times I tried to install it I felt it was far too opinionated for me to get it to work correctly, like other software "bundles" of its kind that want to take control of the entire process of setting up ports, networking, storage, certificates etc..., instead of just hanging down from stuff that I have already prepared for it (like my own domain with my own cert).
Like, as a piece of software it's something I'd absolutely use... if someone else sets everything up for me.
I thought you could install as a docker container?
You can, but honestly no idea how to handle stuff like the certs from that point on. Most other software on docker lets me eg.: just bind-mount the host's directory with the certs I want to use - or just not even know about SSL in the first place and just let me reverse-proxy the access in (like, say, a simple static page web server).
But, like I said, the last times I tried to get into it, it tried its darnest to get in my way. If that's changed since then, that'd be great.
There is a docker container setup with automatic lets encrypt and proxy. Can search around for it.
Hmmm maybe that's the one that tries to do everything on its own instead of using the stuff I've already set up. Had similar issues with eg.: Nextcloud.
I've been looking for an alternative "the actual XMPP service only, nothing else that can be sourced by the host" container setup but there doesn't seem to be any.