Workflows

THIS IS A STEP-BY-STEP GUIDELINE ON THE APPLICATION DEPLOYMENT.

This app has 4 workflow environments namely:

• Development
• Review
• Staging
• Production

1. The dev environment.

This is the application's core environment. This is built locally by the contributing developer where they run the application in development mode to test the output on their local computer via localhost. In this mode, only the user who run the app on their computer are able to see the changes they introduce to the app whether they add, remove or modify any line of code that makes up the app.

2. The review environment.

This is the environment used while reviewing changes made on the app via pull requests. This is built by the review_app_deploy workflow and it runs every time a branch opens a pull request is opened, re-opened or synchronized. The workflow updates any time a commit is made on the branch and the changes gets updated on the application automatically on a successful build of the workflow. The review applications run in review mode via a Heroku pipeline and URL is created following the pipeline name and the pull request's number (e.g: devpulse-review-app-.herokuapp.com). In this mode, anyone user can access the app online through the provided link and are able to see the changes introduced to the app.

3. The staging environment.

This is the release candidate, and this environment is normally a mirror of the production environment. The staging area contains the "next" version of the application and is used for final stress testing and client/manager/P.O approvals before going live. The staging application run in production mode via a Heroku pipeline and URL is created following the pipeline name (e.g: devpulse-staging.herokuapp.com). In this mode, anyone user can access the app online through the provided link and are able to see the pre-production version of the app.

4. The production environment.

This is the currently released version of the application, accessible to the client/end users. This version preferably does not change except for during scheduled releases. The production application run only the changes on the main branch in production mode via digital ocean droplet and URL is created the application's domain name (e.g: devpulse.co). In this mode, anyone user can access the app online through the provided link and are able to see the latest release version of the app.