Run a jabber server: Difference between revisions
No edit summary |
|||
| Line 16: | Line 16: | ||
See [[Installing ejabberd]] for instructions on building ejabberd 2.0.0 from source on Ubuntu 7.10, with the required OLPC patches. |
See [[Installing ejabberd]] for instructions on building ejabberd 2.0.0 from source on Ubuntu 7.10, with the required OLPC patches. |
||
RPM packages for Fedora 7 are available from [[XS Software Repositories]]. |
|||
RPM packages are slightly out of date: See [http://people.collabora.co.uk/~robot101/olpc-ejabberd/ here] for ejabberd 2.0.0 beta 1 packages. |
|||
For developers, more details on the ejabberd configuration are here: [[Ejabberd Configuration]] |
|||
If you get a community server up, consider adding it to [[Community Jabber Servers]]. |
If you get a community server up, consider adding it to [[Community Jabber Servers]]. |
||
Revision as of 18:53, 27 March 2008
OLPC collaboration uses a Jabber server (with a few extra modules and patches) to scale beyond wireless mesh range.
G1G1
For Give 1 Get 1 users, there is no working Jabber server configured by default, since we cannot handle arbitrary numbers of users on a single server. Look at Community Jabber Servers to see if someone is running a community server you can use.
Then use the Sugar Control Panel to change the jabber server on your XO.
Running your own server
Currently we only recommend running ejabberd with OLPC-specific patches.
See Installing ejabberd for instructions on building ejabberd 2.0.0 from source on Ubuntu 7.10, with the required OLPC patches.
RPM packages for Fedora 7 are available from XS Software Repositories.
For developers, more details on the ejabberd configuration are here: Ejabberd Configuration
If you get a community server up, consider adding it to Community Jabber Servers.