...
The technology is based on git repositories for which each client will have one. The git repository contains all configuration files that are pulled to the client system and then the auto-deploy script is run. Given client specific configuration repositories are hosted at Practice Insight private servers, only users having credentials assigned by PI will have access.
The following describes the overall functionality. For deployment of new empty DMS or restoring from backup, see this specific page in addition to the below information.
Git repositories involved in the process are:
...
https://stash.practiceinsight.io/stash/projects/DMSCLIENT/repos/<clientname>/browse
...
Basic method of use:
- Fork Default template to client specific repository with <clientname>;
- Edit configuration files in client specific git repository as required for specific client’s DMS environment – make sure changes are pushed to repository;
- Create folder ~/deploy/config/ to store configuration files and clone client specific repository into this folder;
- Create folder ~/deploy/deploy_script/ to store deploy script logic files and clone client specific repository into this folder;
- cd into ~/deploy/deploy_script/ folder and run „./deploy.sh“ with necessary options.
...