Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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 – make sure changes are pushed 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
    languagebash
    git clone ssh://git@stash.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
    languagebash
    git clone ssh://git@stash.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
    languagebash
    git clone ssh://git@stash.practiceinsight.io:7999/dmsclient/restore_script.git ~/deploy/restore_script

Steps to create empty nuxeo repository:

Go to the  ~/deploy/restore_script/ and start 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 empty DMS containers can now be started with using the deploy.sh scriptdeployed and the DMS started up by cd'ing into  ~/deploy/deploy_script/ folder and running "./deploy.sh" with necessary options. For options, see here.

Steps to restore from backup (Transfer from non-zc to zc):

      6. Go to the  ~~/deploy/restore_script/ and set to modify config.sh configuration file to specify the paths to the backup files in config, and run "./create.sh      7. Start create.sh script;" 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, see here.