5,705
edits
Changes
Jump to navigation
Jump to search
Line 24:
Line 24: − + − + Line 37:
Line 37: − '''TODO''' Initial install configuration, needs to be added to puppet recipes:+ − + − − You can check how many users are registered with: − − # ejabberdctl stats registeredusers
→Notes
|-
|-
!scope="row" | Home
!scope="row" | Home
|{{Code|/srv/ejabberd}}
|''installed from native packages''
|-
|-
!scope="row" | Logs
!scope="row" | Logs
|{{Code|/srv/ejabberd/site/var/log/ejabberd}}
|{{Code|/var/log/ejabberd}}
|-
|-
!scope="row" | Main service
!scope="row" | Main service
|}
|}
Initial install configuration that was done:
* create ''admin'' user
* create ''admin'' user
* add [http://wiki.laptop.org/go/Installing_ejabberd#Installing_ejabberd_from_source_with_OLPC_patches 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. Thus, ejabberd database is being resetting from daily cron task using {{Code|/backup/ejabberd-spool.tar.gz}} initial db.
== Upgrade notes ==
== Upgrade notes ==
Upgrade will be triggered on every puppet session, vcs repository will be rebased to the HEAD commit.
Upgrade will be triggered on every puppet session, vcs repository will be rebased to the HEAD commit.