On Sun, Jun 2, 2013 at 6:22 PM, Ali Lown <[email protected]> wrote:
> I did make some changes to the prosody configuration page yesterday to
> bring it more up-to-date. Is this still incorrect?
Yes, it looks mostly correct, just 2 things:
- The prosody federation port that is mentioned there (5678) is not
consistent with the port specified in the DNS records at the federation
wiki page (5269), so either page should be modified.
- It's still mentioned that "(But note that federation will need SSL)",
right after mentioning that you don't need to enable SSL if you don't have
keys for your server. Which is rather confusing. Is SSL needed, or is it
not? I got the impression it's needed only if the other servers you want to
federate with use SSL (which in an ideal world, would be all of them). Is
that correct?
Additionally, a suggestion:
Prosody config files allow to "include" third files while parsing the main
config file. In debian sid, files at /etc/prosody/conf.d are automatically
included. In other distros, you can add a simple line "include file.lua" to
the general config file.
This means we could add an ant target (soon maven?) to auto-generate the
prosody configuration. The user would only need to sudo copy it wherever
it's "include"d. This makes sense knowing that the prosody config directly
depends on the settings given for the server-federation-config ant target.
I know that prosody isn't the only xmpp server in the world, but it seems
to be de-facto choice of server for xmpp noobs like me, so it wouldn't hurt
to help those people a bit more.
If that sounds good, I offer to create such a target (or should I wait for
maven migration to be finished?).
> @Michael: Can you give Bruno edit access to the wiki?
My username/login is "stenyak".
--
Saludos,
Bruno González
_______________________________________________
Jabber: stenyak AT gmail.com
http://www.stenyak.com
