Difference between revisions of "Obsolete Service/jabber"

From Sugar Labs
Jump to navigation Jump to search
Line 40: Line 40:
  
 
* create ''admin'' user
 
* create ''admin'' user
* add [http://wiki.laptop.org/go/Ejabberd_Configuration Online] shared roster group from web ui.
+
* add [http://wiki.laptop.org/go/Installing_ejabberd#Installing_ejabberd_from_source_with_OLPC_patches Online] shared roster group from web ui.
  
 
There's a problem with scaling up after more than a few dozens of users have been registered. All users who weren't logged in for 2 weeks will be deleted from cron job.
 
There's a problem with scaling up after more than a few dozens of users have been registered. All users who weren't logged in for 2 weeks will be deleted from cron job.

Revision as of 05:42, 4 March 2011

Hostnames

Hosted on

Machine/housetree/jita

Administrative contact

jabber AT sugarlabs DOT org

Sysadmins

For non-emergency calls, preferably send email to the administrative contact.

Notes

ejabberd instance default for upstream sugar shell.

Home /srv/ejabberd
Logs /srv/ejabberd/site/var/log/ejabberd
Main service ejabberd
Admin Web UI http://jabber.sugarlabs.org:5280/admin

TODO Initial install configuration, needs to be added to puppet recipes:

  • create admin user
  • add Online shared roster group from web ui.

There's a problem with scaling up after more than a few dozens of users have been registered. All users who weren't logged in for 2 weeks will be deleted from cron job.

You can check how many users are registered with:

# ejabberdctl stats registeredusers

Upgrade notes

Upgrade will be triggered on every puppet session, vcs repository will be rebased to the HEAD commit.