Obsolete Service/jabber: Difference between revisions
| Line 42: | Line 42: | ||
* add [http://wiki.laptop.org/go/Ejabberd_Configuration Online] shared roster group from web ui. | * add [http://wiki.laptop.org/go/Ejabberd_Configuration 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. | 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: | You can check how many users are registered with: | ||
Revision as of 05:30, 10 January 2011
Hostnames
Hosted on
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.