This page describes the method to use the auto-deploy technology for creating a new empty DMS environment, and for restoring a new DMS environment from a backup.

Git repositories involved in the process are:

i)      Deploy script: This contains the script logic.

https://stash.practiceinsight.io/stash/projects/DMSCLIENT/repos/deploy_script/browse

ii)     Default template: This contains a template for the client-specific configuration repository.

https://stash.practiceinsight.io/stash/projects/DMSCLIENT/repos/default_config/browse

iii)    Client repository: This will contain the client specific repo.

https://stash.practiceinsight.io/stash/projects/DMSCLIENT/repos/<clientname>/browse

vi)    Restore script repository: This contains the script and service files to create new document repository.

 https://stash.practiceinsight.io/stash/projects/DMSCLIENT/repos/restore_script/browse

v)     Import script repository: This contains the script and service files to create new document repository.

 https://stash.practiceinsight.io/stash/projects/DMSCLIENT/repos/import_script/browse

Common deployment steps:

  1. Fork Default template to client specific repository with <clientname>;
  2. Edit configuration files in client specific git repository as required for specific client’s DMS environment – make sure changes are pushed to repository;
  3. Clone client specific repository to ~/deploy/config/ to store configuration files (be sure to change ${clientname} variable to match the client specific repo name):

    git clone ssh://git@stash.practiceinsight.io:7999/dmsclient/${clientname}.git ~/deploy/config
  4. Clone deploy script repository to ~/deploy/deploy_script/ to store deploy script logic files:

    git clone ssh://git@stash.practiceinsight.io:7999/dmsclient/deploy_script.git ~/deploy/deploy_script
  5. Clone restore script repository to ~/deploy/restore_script/ to store restore script logic files:

    git clone ssh://git@stash.practiceinsight.io:7999/dmsclient/restore_script.git ~/deploy/restore_script

Steps to create empty nuxeo repository:

Go to the  ~/deploy/restore_script/ and run "./create.sh" script.

After successful finish of the script you will have an empty nuxeo repository with Patricia workspace created with proper permissions and a settings.xml template for client environment specific modification.

The DMS containers can now be deployed and the DMS started up by cd'ing into  ~/deploy/deploy_script/ folder and running "./deploy.sh" with necessary options. For options, see here.

Steps to restore from backup (Transfer from non-zc to zc):

Go to ~/deploy/restore_script/ to modify config.sh configuration file to specify the paths to the backup files, and run "./create.sh" script.

After successful finish of the script you will have a DMS restored from the backup.

The DMS containers can now be deployed and the DMS started up by cd'ing into  ~/deploy/deploy_script/ folder and running "./deploy.sh" with necessary options. For options, see here.

Steps to import documents:

  1. Create empty repository following the instructions above. 

  2. Clone client specific repository to ~/deploy/import_script to store import script:

    git clone ssh://git@stash.practiceinsight.io:7999/dmsclient/import_script.git ~/deploy/import_script
  3. Set the path of the documents to import in the import_script/config/import.conf
  4. Start import_script/import.sh
  5. When the import process finished, check the final output of the compare script to be sure everything is imported.

The DMS containers can now be deployed and the DMS started up by cd'ing into  ~/deploy/deploy_script/ folder and running "./deploy.sh" with necessary options. For options, see here.