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 (PI internal links only):

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

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. Most of the times, only changes to containers.conf, dms.conf, and, if applicable, postfix-config.sh will need to be made. Edits to the remaining files (e.g. commands.conf) will be rare and only required in special situations. They should only be made if you are sure you understand what you are doing. Make sure changes are pushed back to repository;
3. Create folder /storage/ which will be the default storage location for all DMS-related information. If you want to use a different storage location, storage.conf must be adapted. Please observe not under item 2;

4. 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@support.practiceinsight.io:7999/dmsclient/${clientname}.git ~/deploy/config

5. Clone deploy script repository to ~/deploy/deploy_script/ to store deploy script logic files:

   git clone ssh://git@support.practiceinsight.io:7999/dmsclient/deploy_script.git ~/deploy/deploy_script

6. Clone restore script repository to ~/deploy/restore_script/ to store restore script logic files:

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