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
IMO Snikket (XMPP) is the easiest all-in-one solution with audio/video chat at the moment. Pretty good on resources too.
I currently host a Matrix Synapse server, but:
I have gone down the matrix rabbit hole but i choose Continuwity, which is the successor to Conduwuit after the community drama.
It's a rust server alternative to synapse, it's lightweight and works very well.
Fuck synapse, it's a colossal pain for small servers, not worth it. I also actively avoid anything related to the company behind it since I think they poison what matrix could be.
I wish I started with XMPP, but now I am selfhosted on matrix, so.
Lol, exact same situation here.
Quick question, did the migration to continuwuity break calls for you as well?
Never used calls...
Snikket locked my docker service up, their documentation sucks for when you want to use your own reverse proxy or bind it behind a docker network and not the host.
I haven't run snikket before, but it looks straightforward to me. Maybe the documentation has improved?
Doesn’t cover Traefik, plus the docker-compose.yml contains 4 separate images and researching into them didn’t provide much info.
snicket_proxy
,snikket_certs
,snikket_portal
andsnikket_server
. All four of these images bind to the host but if I am supplying my own reverse proxy then bothsnikket_proxy
andsnikket_certs
are redundant right? Or do they serve another purpose? And if I wanted to take them off the host network, follow their firewall guide and expose the necessary ports manually behind a docker bridge network what images do I bind those ports to? When I tried binding them all tosnikket_server
that’s when my docker service crashed and I gave up.I see. Yeah, that compose file is gross unless you're running this on a dedicated vps, and even then...
Thanks! I didn't know about this and it is from the developers of prosody (currently mentioned in the top reply) so will definitely be trying it! https://blog.prosody.im/introducing-snikket/
Trying Tuwunnel, works very well