Midgard’s new replication service has been under work since January. Now the work is finally starting to bear fruit, as we’re doing the first tests with real production data.
This week lots of functionality has been added to the system, including scheduled replication runs (for scheduled publication) and a nice debug view for seeing the replication status of an object:
This view should make it easier to figure out what replication actions have been undertaken with the object. In the example above, the object was imported twice from an external source (probably two edits), and then also exported twice for a replication queue. The queue however has not yet been processed and so the object is still not fully replicated to the external service.
The replication queues are managed in a user interface on the MidCOM site itself. Site administrator can set up multiple replication pipelines including archival or emailing of backups and HTTP-based replication to remote hosts:
Updated 2007-04-12: Replication seems to work quite fine, but we’re still running tests with it. Those who want to play with it will benefit from the setup instructions draft.