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:
- 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
Dumbest answer: I didn't find a one click solution on casaOS.
No idea what the heck casaOS, but here you get your turnkey XMPP servers (if you really don't want to use a distro that packages prosody/ejabberd, which are all the ones worthy to be used anyways?):
https://snikket.org/
https://www.process-one.net/en/ejabberd/downloads/
casaOS is a docker-compose simplified one click solution, like unraid or heimdall.
Sure I tried to add xmpp to my apps, but finding the right one on xmpp is like the first experience with Linux ... too many alternatives. I tried openfire because it sounds good with a compose file and proxy all to my caddy server. But I am stuck actually (the last 10 min), and I am unable to decide if ejabberd is better.
If your system is based on docker, couldn't you just use the official docker image I linked? Besides, I wouldn't recommend openfire, not because it's not a capable server (it's been to long since I tried it to have a meaningful opinion), but because it has less widespread usage than ejabberd/prosody, and by extent, probably less resources to help you configure it to your needs.
I know it's not the topic of this thread, but you are not making a convincing case (to me!) for a "docker-compose simplified one click solution" that pulls you away from the most popular and well maintained alternatives :)
And you will also likely encounter things down the road pertaining to firewall configuration, domain name resolution and port multiplexing that containerization will turn into a configuration and troubleshooting nightmare, so… enjoy! (or not)