Backend development and deployment guidelines

Backend development and deployment guidelines

Git

We want to work as if we are doing trunk development but the whole team uses git flow with a branch system that looks like production <- staging <- development <- feature. In order to achive this we PR directly to production and we do back merges from production to staging and development (automatic script on the works). this is how this would look like:

1. PR to production with version bump
2. Merge production to staging with version bump
3. Merge staging to development (version does not matter)

Deployments

When the new release has been generated in Github you can proceed with the deploy.

deploy staging first, test everything as expected then deploy production and test it in production.

if there is a deploy going on we need to wait to deploy again.

We want to always use "fast_deploy" if possible, whenever we are working on something that requires a migration or reindex, the backend team will discuss a custom solution or go the old route (create a migration and merge to development instead).

the new version should be compatible with the old one.

Todos

• Rollback in case deploy goes wrong (now rollback can only be performed manually)
• Have control over the release version deployed (do not assume always latest version)