Quality Assurance
Warning
This page is deprecated and may be removed soon.
We maintain a staged deployment process for quality assurance. You can find a diagram below showcasing the main structure, and more details in each section below (testing - staging - production).
Test deployments are automated with Heroku, and available for each pull request.
Please note all test apps use the same postgres database - which means that a maximum of 22 test apps will function (the maximum default connections to a postgres database).
Auto deployments self-destruct after 48 hours and need to be reactivated by a maintainer if necessary. This is the case because each auto-deployment accrues costs.
The staging branch is automatically deployed to Heroku. Sometimes we may not want to deploy immediately to the production branch and test a set of changes here first.
An example scenario is when we want to do user testing in a safe environment. This is on an ad hoc basis.
The production branch is the main branch.
ResearchEquals is deployed on a continuous basis using Flightcontrol. This is managed in the /flightcontrol.json file (root directory).
There is also an automated deploy of the main branch on Heroku to ensure deployment issues are not a result of either Heroku or Flightcontrol.