MidRepository 0.9 (Alpha) README
********************************
Copyright (C) 2003 David Schmitter, Dataflow Solutions GmbH <schmitt@dataflow.ch>

Description
-----------

MidRepository is a versioning and workflow system for Midgard. It represents Midgard DBs as collections of repligarded objects under CVS control. All changes in the midgard objects are automatically reflected in CVS and a global meta-information DB. (Groups of) Midgard DBs are connected to CVS branches. You can specify fine-grained workflow rules for moving around objects between the branches / DBs.
For every branch (staging / live), there is a central backend DB that contains the authoritative versions of the objects. Changes in the frontend DB(s) are imported into the backend DB, written to CVS and delivered to all frontend DBs.

Getting oriented
----------------

You can have an unlimited number of DBs connected to an unlimited number of branches. There is always: 
- 1 central DB for the whole system, storing all the meta information
- 1 central DB for every branch that contains the authoritative data. The content in this DB is not directly modified.
- At least 1 frontend DB for every branch. This is where content should be modified. 

Modifications in the frontend DBs are automatically replicated (on mgd_create/update/delete_xxx) to the central DB for the branch. Later modifications overwrite earlier ones, but all revisions are recorded.

Info about the default install (see INSTALL):
It's a basic staging / live setup with 1 meta db, 1 backend live, 1 backend staging, 1 frontend live and 1 frontend staging DB.

- Libraries in /var/mgd/lib
- Configuration in /var/mgd/lib/vcconfig.php
- Example workflow configuration in /var/mgd/etc/workflow.xml
- Spool directories in /var/spool/mgd
- Blobs under /var/www
- /var/mgd/bin/everymin.php replicated stuff in and out
- /var/mgd/bin/dump.php dumps any changes in the frontend DBs into the spool directories.

See API documentation in ./apidoc/
	
See installation instructions in ./INSTALL
