|Alias||Purpose||Deployment Build (update version)||Reset build (restart and clean data)||Docker image tag||Backups||Cleans data on deployment|
Metadata Sharing Builder
Deploy mdsbuilder (manually)
|uat-platform.openmrs.org||OpenMRS Platform Release Testing||UAT Platform (manually)||Redeploy uat-platform (daily)|
|Alias||Purpose||Deployment Build (update version)||Reset build (restart and clean data)||Docker image tag||Owner||Backups||Cleans data on deployment|
|qa-refapp.openmrs.org||OpenMRS RefApp automated QA Testing (from CI)|
Reference Application Distribution (on green build)
OpenMRS RefApp Community modules
(modules are manually installed)
Modules refapp (manually)
Redeploy modules-refapp (manually)
(Override customised variable 'destroy.data' to false to just restart it without losing data)
|demo.openmrs.org||OpenMRS RefApp demo site (stable version)|
|Redeploy docker demo (daily)|
|uat-refapp.openmrs.org||OpenMRS RefApp Release Testing|
UAT refapp (manually)
|Redeploy uat-refapp (weekly)|
Developer Test Environments
When we have the resources available, we will try to help developers in the OpenMRS community in hosting & demonstrating their OpenMRS-related work. Since resources are limited, these hosted developer test environments should be reserved for community collaboration projects and used for short periods of time. Examples would include hosting an instance of OpenMRS to demonstrate or get user feedback/testing of a feature or module during a community sprint or development spike.
In most cases, we expect developers to use their own resources for short-term hosting (e.g., a GSoC student can host her project in Digital Ocean).
If you require a development test server (and it has been agreed in talk), please submit an ITSM ticket and describe your needs. Only a limited number of test servers are available, so please let us know when you are done so the resources may be used by someone else. Setting it up can take a few hours, so please submit your ticket at least a week in advance:
In your request, include:
- Your name, OpenMRS ID, and developer stage.
- A short description of how the test server will be used.
- The date until the server is needed (a few weeks)
- A statement that you understand you will be responsible for the application and troubleshooting (they are running in docker)
- A link to the pull request with your application How to deploy a new application to our infrastructure
|Alias||Purpose||Deployment Build (update version)||Reset build||Docker image tag||Expires||Owner||Backups||Cleans data on deployment|
|Sync demo environment||None.|
|Sync demo environment||None.|
You should be able to run all dockerised environments (with database and data) locally using docker-compose and docker. Each folder has a readme file explaining how to do it.
Every environment is using a different docker image tag; when the tag is pushed docker hub is configured to call a webhook and deploy the new version of the image/application. The docker autodeploy is defined in ansible and deployed to required docker hosts.