recommend ejabberd in FAQ

This commit is contained in:
Daniel Gultsch 2019-10-15 11:04:12 +00:00 committed by GitHub
parent 9bea8074ab
commit 537c8bb300
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -125,11 +125,13 @@ Using your own domain not only gives you a more recognizable Jabber ID, it also
Learn more about [conversations.im Jabber/XMPP domain hosting](https://account.conversations.im/domain/).
##### Running your own
If you already have a server somewhere and are willing and able to put the necessary work in, one alternative-in the spirit of federation-is to run your own. We recommend either [Prosody](https://prosody.im/) or [ejabberd](https://www.ejabberd.im/). Both of which have their own strengths. Ejabberd is slightly more mature nowadays but Prosody is arguably easier to set up.
If you already have a server somewhere and are willing and able to put the necessary work in you can run your own XMPP server.
For Prosody you need a couple of so called [community modules](https://modules.prosody.im/) most of which are maintained by the same people that develop Prosody.
As of 2019 we recommend you use [ejabberd](https://ejabberd.im). The default configuration file already enables everything you need to pass the [Conversations Compliance Suite](https://compliance.conversations.im). Make sure your Linux distribution ships a fairly recent version.
If you pick ejabberd make sure you use the latest version. Linux Distributions might bundle some very old versions of it.
With a little bit of effort [Prosody](https://prosody.im) can be configured to support all necessary extensions as well. However you will have to rely on so called [Community Modules](https://modules.prosody.im/) of varying quality. Prosody can be interesting to people who like to modify their server and create / prototype own modules.
Performance wise - for small deployments - both ejabberd and Prosody should be fine.
#### Where can I set up a custom hostname / port
Conversations will automatically look up the SRV records for your domain name