...
- 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. 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, 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. 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@edmssupport.pace-ip.com:7999/dmsclient/${clientname}.git ~/deploy/config
Clone deploy script repository to
~/deploy/deploy_script/
to store deploy script logic files - if you start out from the preconfigured DMS VM images, this step can be skipped:Code Block language bash git clone ssh://git@edmssupport.pace-ip.com:7999/dmsclient/deploy_script.git ~/deploy/deploy_script
Clone restore script repository to
~/deploy/restore_script/
to store restore script logic files - if you start out from the preconfigured DMS VM images, this step can be skipped:Code Block language bash git clone ssh://git@edmssupport.pace-ip.com:7999/dmsclient/restore_script.git ~/deploy/restore_script
- Update the deploy and restore scripts as per below instructions.
- Create an empty nuxeo repository or restore from a backup of a DMS (see below);
- Copy any fonts you intend using to
/storage/nuxeo/fonts/
(unless you are using a different storage location; if so, adapt accordingly); - 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.
...