[Freedombox-discuss] prosody vs ejabberd

Nick Daly nick.m.daly at gmail.com
Wed Sep 28 23:57:22 UTC 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bdale Garbee <bdale at gag.com> writes:

> I could use input from people who have *actually used* prosody and/or
> ejabberd about your experiences and the resulting pros and cons of the
> two daemons.  

Bdale, I've gone with ejabberd for my plugserver setup [0].  ejabberd is
easy to setup by hand and my automatic-setup script is also complete (it
required only dpkg-reconfigure to be up and running).

Pros:

- - Easy to configure via web-interface.

- - Incredibly stable.

- - Used widely (presumably this means the code has also undergone lots of
  review?)

- - Very low memory footprint when not under load (never ran a server with
  more than 5 connected users at a time though).

Cons:

- - The web-configuration tool is a frontend to the database directly,
  bypassing the config files.  If you use the web-configuration, the
  config files themselves are useless.

Nick

0: https://bitbucket.org/nickdaly/plugserver/
- -- 
GPG: 0x4C682009 | 084E D805 31D8 5391 1D27  0DE1 9780 FD4D 4C68 2009
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk6DtGMACgkQl4D9TUxoIAkRIgCfdGEB0edcgLpfhNq30p901VWX
kRcAnjG0MSJgL7fxM+AldezLZCiqzifE
=KzEC
-----END PGP SIGNATURE-----



More information about the Freedombox-discuss mailing list