...
- 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“sh" with necessary options.
Options for deploy.sh:
...
Options can be combined.
Examples:
„
| Code Block |
|---|
./deploy.sh elastic postgres nuxeo -rmc -rmi |
...
./deploy.sh nuxeo cb -rmc |
...
./deploy.sh nuxeo cb -rmc -rmi -vvv |
...
|
Important Notes:
- Restarting of elastic or postgres containers without restaring nuxeo container will break DMS functionality until nuxeo container restart.
- The
deploy.shscript will check if modifications have been made to the files in ~/deploy/config/ that have not been committed/pushed to the client specific git repository (ie. if there is discrepancy between the origin of the client specific git repository and the local configuration files). If such is the case, deploy.sh will not execute but output a corresponding warning and quit. It is important to commit local changes to the repository. After that, run "./deploy.sh" again.