I use this and it's been completely flawless from day one. The documentation is up there with the best I've seen, and the matrix room always has someone willing to help explain further
this post was submitted on 25 Jul 2024
45 points (97.9% liked)
Selfhosted
40669 readers
379 users here now
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!
founded 2 years ago
MODERATORS
Holy crap that is comprehensive. Great timing since I'm about to wipe and redo my server from scratch.
Thanks for sharing!
I've had good luck with Yunohost in the past for a synapse server.
Do I need to remove casaos to use yunohost?
Yeap.. Yunohost is not docker based.
Can it possibly run simultaneously?
Doubtful. Even in VMs I reckon you're gonna have some conflicts ports wise.
I heard conduit.rs has lower memory requirements. Dunno if there's a easy to deploy container tho. Good luck!
If the postgres container doesn't start properly, then something's wrong with the config. Most likely you are trying to expose port 5432 to the host network, but you have postgres already installed there, so the ports conflict.
You can check for those errors with journalctl.
I wrote my own ansible role to deploy/maintain a matrix server and a few goodies (element/synapse-admin). If you're not using ansible you should still be able to understand the deployment logic by starting at tasks/main.yml and following includes/tasks from there.
I prefer Conduit instead of Synapse - it is lighter on resources.
I’ll second conduit. You can tune up its caching, reducing the ram usage significantly. It does become a bit painful to sync the mobile clients, but at least it's not gigabytes of ram wasted.
How would I go about using conduit instead of synapse for matrix?
Here is the Conduit Docker deployment guide.
https://famedly.gitlab.io/conduit/deploying/docker.html
I started with the Docker Compose file they provide, and "translated" it into Podman rootless containers for my server. Even with adding the extra work, it was pretty painless.
Weird, conduit.rs links an entirely different Gitlab page - https://gitlab.com/famedly/conduit, with the docs being at https://docs.conduit.rs/deploying/docker.html
Hmm, docs.conduit.rs appears to be an alias for famedly.gitlab.io. I copied the link from the intro in the README.md file in the GiLab repository.
I would try YUNOhost