Deploy and Release

Deploys

We are using https://caprover.com to deploy the app. You can enter our CapRover instance in https://captain.deploy.timeoverflow.org/ to manage some things like: ENV vars, deployments, check the logs, ...

Strategy

• Staging: via CapRover CLI or via CapRover UI
• Production: each push to master branch is deployed automatically

Production Release 🚀

NOTE ℹ️ The smaller the release, the easier it gets to collect the changes and the lower the risk it may introduce.

1. Open a pull request from develop to master. List the introduced pull requests in its description: the ones that showed up in the search you did in the previous step. Keep in mind this has to be understandable for human beings! And also fun so please, consider adding a funny Gif 😂

   You can take this pull request as a good example.

2. Draft a new release, from the releases section. ⚠️ Make sure you select master as its target.

   As for the version, we follow semver. Unless it's a hotfix, increase the minor version. Increase the patch version otherwise.

   Finally, you can copy and paste the description you added in the pull request you opened in the step 1. Or use the GitHub autofill feature.

   Now you can "Save draft".

3. Once the pull request in the step 1 passed all checks and no one complained, you can merge it. At this point, a new deploy is automatically launched 🚀.

4. You can publish the release we drafted in the previous steps. Please, review the description first and publish it.