Page History

...

i)      Deploy script: This contains the script logic.

httpshttp://stash172.20.practiceinsight.io/stash32.20:7990/projects/DMSCLIENT/repos/deploy_script/browse

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

httpshttp://stash172.20.practiceinsight.io/stash32.20:7990/projects/DMSCLIENT/repos/default_config/browse

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

httpshttp://stash172.20.practiceinsight.io/stash32.20:7990/projects/DMSCLIENT/repos/<clientname>/browse

...

1. PI forks Default template to client specific repository with <clientname> upon request;
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 (see below for some guidance on the DMS heap configuration in dms.conf). Edits to the remaining files (e.g. commands.conf) will be rare and only required in special situations, such as, for example, if proxy setups need to be catered for. They should only be made if you are sure you understand what you are doing. Make sure changes are pushed back to repository;
   Please make sure to change the standard NUXEO_PASSWORD in the dms.conf.
3. Copy any fonts you intend using to /storage/nuxeo/fonts/ (unless you are using a different storage location; if so, adapt accordingly);
4. Create folder ~/deploy/config/ to store configuration files and clone client specific repository into this folder;
5. Create folder ~/deploy/deploy_script/ to store deploy script logic files and clone client specific repository into this folder;
6. Create an empty nuxeo repository, restore from a previous DMS version (using the restore scripts - check here for details);

7. Copy any fonts you intend using to the storage location (default is /storage/nuxeo/fonts/);

8. cd into  ~/deploy/deploy_script/ folder and run "./deploy.sh" with necessary options.

...

The following heap settings to be set in dms.conf present some guidance based on user count. Note that other parameters such as status of the project (eg. document background analysis phase or only production phase), etc. play into these values which may thus be subject to change.
It's usually recommended to set the same value to the XMS and XMX part, especially for elasticsearch, as the heap extension is a costly operation. Unequal values can lead to experiences of short freezes. The XMS value will be ignored in newer DMS versions.

...