Page History

...

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. Clone client specific repository to ~/deploy/config/ to store configuration files (be sure to change ${clientname} variable to match the client specific repo name):

   Code Block
   language bash
   git clone ssh://git@support.practiceinsight.io:7999/dmsclient/${clientname}.git ~/deploy/config

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

   Code Block
   language bash
   git clone ssh://git@support.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:

   Code Block
   language bash
   git clone ssh://git@support.practiceinsight.io:7999/dmsclient/restore_script.git ~/deploy/restore_script

6. Create an empty nuxeo repository or restore from a backup of a DMS (see below);
7. Copy any fonts you intend using to /storage/nuxeo/fonts/ (unless you are using a different storage location; if so, adapt accordingly);
8. Deploy and startup the DMS containers by cd'ing into  ~/deploy/deploy_script/ folder and running "./deploy.sh" with necessary options. For options and further instructions, see here.

...