Set up deployment pipeline for prod

[deammer]

We'd like to create a prod environment on Clever Cloud and make it easy for admins to deploy code.

Some ideas:

• we could create a new prod branch and auto-deploy it to a prod environment (related to Set up semantic release #357)
• we want the database to be completely separate from dev
• we should document the release process and lock it down to a select few people

[juliandm]

Hi which points of this issue are still relevant? Seems that a continuous pipeline is active since all merges to saga are deployed via the clever cloud integration.

Furthermore we could think about two databases: one for preprod envs (dev & staging) to cut costs and one for prod. Ideally ofc one for each environment.

[coderbyheart]

As mentioned in #311 we don't have the infrastructure definition persisted as code.
Additionally code pushed to saga does not mean it should automatically be promoted to the production instance without further checks.
I think something like having a prod branch to signal which release should go to production could be a straightforward solution.

[coderbyheart]

Proposal would be to tie this with #357 so we actually have meaningful release versions that end up on the prod instance.

[coderbyheart]

#384 has code to create a new application on Clever Cloud from scratch. The code in there can be used to base the configuration of the production instance on.