Deployment

The Hale Platform can be deployed into four environments, prod, staging, dev and demo. These environments are represented by branches in this repo and by merging your code into these branches you will trigger a build and deployment.

To deploy into each environment we use GitActions. This actions are configured in our cd.yaml file. Here is an example of what the deployment interface looks like:

Deploy to staging or production

Merge or push code to the main branch. This will trigger a deployment to staging. To then deploy to production, you will then have to manually go into the GitActions tab and approve the deployment out to the production environment.

Deploy to dev or demo

Merge or push code to the corresponding branch with the same name. You can check you progress via GitActions workflow chart.

Confirm deployment has been successful

In your terminal run helm list. You should see a timestamp that corresponds to your deployment and status deployed. You can also run kubectl get all. You should see your pods running with a pod status of 2/2 and Running.

Steps to deploy a plugin or Hale theme

1. Make sure plugin or hale theme has changes merged into that repo's main branch.
2. Make sure the version has been updated and new release created.
3. Run CircleCI pp satis which loads the plugin or theme into our Composer repository.
4. Run Composer update in the root of this repo, save and push your changes up to your target branch you wish to deploy to.
5. If pushing to production, you will need to approve manually the deployment from staging to production in GitActions.