In July of 2019 the eDMS Software has changed ownership from Practice-Insight to Pace-Ip.

All Configuration Management that Prior to this Point in time was done to and from the Servers of Practice-Insight have now been moved over to the Servers of Pace-Ip.


Pace-Ip and or Patrix Need your notification

Notification on the time when you want your EDMS Configuration to be updated.


Our tasks are then to

  • Perform a forksync on the client config repo
  • Merge the mismatches in dms.conf by hand
  • Push the result to pace-ip.com


On the Client´s (your) DMS Machine the following has to happen:


  1. Run /root/update_scripts.sh    (This will set the urls for pace-ip in the the deploy script)
  2. Run /root/deploy/deploy_script/deploy.sh (with the flags you need to set)
  3. This will most likely fail, but in the process of this you will be asked to accept the key of pace-ip.com (which you should). This leads to the client config repository now being connected to pace-ip
  4. Now go to /root/deploy/config and perform a git pull
  5. This will download the newly configured configuration files from our server.
  6. Now Run /root/deploy/deploy_script/deploy.sh (with the flags you need to set)
  7. DMS will re-deploy and everything is wonderful


Please Note: the new configuration sets the Version of eDMS to 1.9.8.2.4-2

If you for some reason don´t like that, change it in /root/deploy/config/containers to your desired/known Version. Before you do your final deploy.


Verwandte Artikel