There is no migration and you can not use the same (sub)domain for dendrite you use for synapse. It breaks the federation. If you use matrix.domain.com for synapse, you need to use another domain for dendrite.
I got a 4 CPU / 24Gb RAM Ubuntu 22.04 ARM VPS running on Oracle's "always free" tier. The Synapse and Postgres containers are using about 2% CPU and 1.2Gb of RAM combined. If your strapped for resources, check them out.
The Synapse and Postgres containers are using about 2% CPU and 1.2Gb of RAM combined. If your strapped for resources, check them out.
with 1.16G i can run dendrite and iceshrimp (+redis and +sonic, shared caddy and postgres between both). i wouldn't call synapse the "strapped for resources" server.
Do you have any issues with Spaces rooms not loading on yours or federated homeservers? I tried reinstalling a couple times and could never get them to load in Element, so I ended up just spinning up Synapse which has been working fine.
I've just deployed a Synapse container to work with matrix/Element, only because that's what the guide I was using suggested. Is there any benefit to switching?
Dendrite is supposed to be lighter on resources than Synapse, but I have no evidence other than dev claims. I had no performance issues when running Synapse a couple years ago.
I'm running synapse just fine on an old ThinkPad. Doesn't seem to be terrible on resources. I also have my lemmy instance on the same laptop and don't have any issues with resources.
I am surprised so few people are mentioned conduit here. Last I checked, it was running at only 500 MB of RAM. I don't have any app services installed though, and I'm the only user on my instance.