Version 42 (modified by Dominic König, 12 years ago) ( diff )






The synchronization process is controlled entirely by the local Sahana Eden instance.

The local Eden instance runs the scheduler process, and initiates the update requests when due, while the remote repository merely responds to these requests.

Synchronization Overview

The local Eden instance first downloads the available updates from the remote repository (pull) and imports them into the local database, and then uploads all available updates from the local database to the remote repository (push).

Both pull and push are each a RESTful HTTP-request, using S3XML as data format.



Follow this checklist to configure synchronization:

  1. Check the Prerequisites
  2. Login as administrator at the remote site and register the '''local''' site
  3. Login as administrator at the local site and
    1. Register the '''remote''' site
    2. Configure the resources to synchronize
    3. Set up the Synchronization Schedule
  4. Start the worker process at the local site


Both sites must have Sahana Eden installed and running. To avoid problems with different database structures, both Sahana Eden instances should always use the same version of the software.

Decide which one is the local and which the remote site. The remote site is typically a permanently and publicly accessible Sahana Eden instance, while the local site could be a protected site, or with only temporary network access. See Synchronization Overview to understand the situation.

While performing synchronization jobs, the local site must be able to establish a connection to the remote site over the network using HTTP.

If a proxy server is to be used for the HTTP connection, this can be configured in the Synchronization Settings (proxy authentication is currently not supported).

Check that both instances have the synchronization module enabled in models/ If the sync section is missing from deployment_settings.modules, then add it as follows:

deployment_settings.modules = OrderedDict([


    # Add or uncomment this section, if it is missing or commented:
    ("sync", Storage(
            name_nice = T("Synchronization"),
            description = T("Synchronization"),
            restricted = True,
            access = "|1|",     # Only Administrators can see this module in the default menu & access the controller
            module_type = 0     # This item is handled separately for the menu



Synchronization Homepage

Login as administrator and open the Administration menu. In the left menu, you find the following entries:

Synchronization Menu

Click on Synchronization here to open the homepage of the Synchronization Module:

Synchronization Homepage

Synchronization Settings

Go to the Synchronization Homepage and click Settings to open this page:

Synchronization Settings


This page shows you the UUID (universally unique identifier) of this repository. You will need this identifier to register the repository at the peer site (the local UUID to register at the remote site, and the remote UUID to register at the local site). The UUID is created during the first run of the Sahana Eden instance, and cannot be changed.

To Do the local site:

  • if needed, enter the complete URL of the proxy server (including port number if not 80) that is to be used when connecting to the remote site. Click Save to update the configuration. the remote site:

  • no change required


The scheduled synchronization jobs are performed by a separate asynchronous web2py worker process at the local site.

To Do the local site:

To start the worker process, open a shell on the local server, change into the web2py home directory and run:

python -K eden -Q

(replace "eden" with the name of your Sahana Eden application if necessary)

In more advanced configurations you may want to run this command as a daemon process, e.g. under Linux by:

nohup python -K eden -Q >/dev/null 2>&1 & the remote site:

  • no action required

Repository Configuration

Go to the Synchronization Homepage and click Repositories. This will show you a list of all configured repositories:

Repository Registry

The Open button in each line opens the configuration for the respective repository.

By clicking Add Repository, you can add a new peer repository configuration:

Repository Registration

FieldInstructionsat the local siteat the remote site
NameEnter a name for the repository(for your own reference)requiredrequired
URLEnter the URL of the repositoryrequired-
usernameEnter the username to authenticate at the repositoryrequired-
passwordEnter the password to authenticate at the repositoryrequired-
proxyEnter the URL of a proxy server to connect to the repository, if different from the Synchronization Settingsfill in as needed-
Accept Pushescheck this if the repository is allowed to push updates-set as needed
UUIDEnter the UUID from the Synchronization Settings of the repositoryrequiredrequired

To Do the local site:

  • add a repository configuration for the remote site the remote site:

  • add a repository configuration for the local site

Resource Configuration

  • tbw

Synchronization Schedule

  • tbw

Synchronization Log

Go to the Synchronization Homepage and click Log. This shows you a list of all prior log entries for all repositories.

If you instead want to see the log entries only for a particular repository, go to the Synchronization Homepage, click Repositories, then Open the respective repository configuration and go to the Log tab:

Repository Log

Note: the newest entries are shown on top of the list.

Click on Details for a log entry to see the complete entry:

Repository Log Entry

Date/TimeDate and time of the transaction
RepositoryName of the repository synchronized with
Resource NameName of the resource synchronized
ModeTransaction mode (pull or push) and direction of transmission (incoming or outgoing)
ActionAction performed to resolve problems (if any)
ResultResult of the transaction
Remote ErrorTrue if there was an error at the remote site
MessageThe log message

See S3/Synchronization

Attachments (10)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.