...
- 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. They should only be made if you are sure you understand what you are doing. Make sure changes are pushed back to repository; - 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; - Copy any fonts you intend using to
/storage/nuxeo/fonts/
(unless you are using a different storage location; if so, adapt accordingly); 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
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
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
- Copy any fonts you intend using to
/storage/nuxeo/fonts/
(unless you are using a different storage location; if so, adapt accordingly).
Steps to create empty nuxeo repository:
Go to the ~/deploy/restore_script/
and run "./create.sh
" script.
After successful finish of the script you will have an empty nuxeo repository with Patricia workspace created with proper permissions and a settings.xml template for client environment specific modification.
The DMS containers can now be deployed and the DMS started up by cd'ing into ~/deploy/deploy_script/
folder and running "./deploy.sh
" with necessary options. For options and further instructions, see here.
Steps to restore from backup (Transfer from non-zc to zc):
Go to ~/deploy/restore_script/
to modify config.sh configuration file to specify the paths to the backup files, and run "./create.sh
" script.
After successful finish of the script you will have a DMS restored from the backup.
The DMS containers can now be deployed and the DMS started up by cd'ing into ~/deploy/deploy_script/
folder and running "./deploy.sh
" with necessary options. For options and further instructions, see here.