Deployment

Frontend

Production deployment

For production, push to branch “production”, the GitHub hook “auto-merge.yml” runs and merges “production” to “main”.

Vercel is connected to “main” and a build is triggered automatically.

Staging/Preview deployment

For a staging deployment, push to branch “staging-backend-vercel”, the GitHub hook “auto-merge-staging-backend.yml” runs and merges “staging-backend-vercel” to “staging-backend”.

Vercel is not going to automatically build, you have to manually create a new deployment.

Note that this branch uses the staging backend at https://staging.cms5.nelios.com/ , also keep in mind that the staging backend might not be running all the time to save resources. You can start it by following the guide here or by pushing in the staging backend branch.

Backend

Production deployment

For production, we use the “main” branch, but PRs are required. Create your branch, push it and create a new PR. Once merged, a GitHub action will be triggered to automatically deploy and build the production server.

Note that it is safe for a build to fail, if it does, the server will not point to that build.

Staging deployment

For staging, push to branch “staging”, a GitHub action will be triggered and automatically deploy and build the staging server. If the server is not running it will start.

GitHub actions

You can check the action logs from here