undefined | Better HN

0 pointsmajewsky9y ago0 comments

I have a virtual server (1 CPU + 1 GiB RAM) running nginx, murmur and Prosody. free(1) reports 80 MiB used memory, thereof 10 MiB for Prosody. (I just have one active account, though: myself.)

So unless you're planning on hosting hundreds or thousands of users, you should be fine IMO.

0 comments

giancarlostoro9y ago

I had not even 3 users... I was running a Java one, looks like Prosody is worth it's salt. Does it support E2E and other features that Conversations supports? :)

Edit:

I was running it on a DigitalOcean box with only 512MB of ram at the time, which I found a bit silly that I would come back and the server was down, but it was a different XMPP server than Prosody.

catdog9y ago

You probably used Openfire, known to be a memory hog and a bit unstable. Simply go for prosody and you should be fine (ejabberd should also be OK). Some newer XEPs which you may want to have with Conversations are not supported OOTB in prosody (yet) but there are plugins distributed separately [1][2].

[1] https://modules.prosody.im/ [2] https://prosody.im/doc/installing_modules

giancarlostoro9y ago

Yes that was the culprit! OpenFire sounds like it... I wanted something simple to setup, without too many terminal incantations. Thanks for the information, it's invaluable.

majewskyOP9y ago

E2E does not need support from the server. Regarding Conversations, I'm using it with my server and it seems to be working fine, although I have not tested every single XEP supported by Conversations.

giancarlostoro9y ago

This is true, it's kind of easy to forget how E2E works sometimes, thanks!

j / k navigate · click thread line to collapse

0 comments

giancarlostoro9y ago

I had not even 3 users... I was running a Java one, looks like Prosody is worth it's salt. Does it support E2E and other features that Conversations supports? :)

Edit:

I was running it on a DigitalOcean box with only 512MB of ram at the time, which I found a bit silly that I would come back and the server was down, but it was a different XMPP server than Prosody.

catdog9y ago

[1] https://modules.prosody.im/ [2] https://prosody.im/doc/installing_modules

giancarlostoro9y ago

Yes that was the culprit! OpenFire sounds like it... I wanted something simple to setup, without too many terminal incantations. Thanks for the information, it's invaluable.

majewskyOP9y ago

giancarlostoro9y ago

This is true, it's kind of easy to forget how E2E works sometimes, thanks!

j / k navigate · click thread line to collapse