deploy the site

[RasmusKard]

Need to explore the best way of going about it.

Needs to match the following criteria:

• Easy and quick re-build and re-deploy with Github Actions
• Not expensive
• Not too hand-holdy

[RasmusKard]

CI workflow

• [x] Pull test DB image from Github Packages (Need to push this and add schema notes to docs)
• [x] Docker compose DB image and Website image
• [x] E2e test
• [x] IF (SUCCESS) push website image to Github Packages
• [x] IF (FAIL) Log test results in Github Actions artifacts and break the workflow

CI improvements

• [ ] Try to persist data of DB image to reduce time during build (initialization with .sql files)
• [ ] Cache playwright install
• [ ] Clean/split up Github workflow YAML files

CD workflow

• [ ] Listen to Github Package changes, if change pull image (Maybe something that only works when there is a "Release" pushed to the repo?)
• [ ] Build image (Probably run e2e test again to be certain that build went fine?)
• [ ] Deploy image
• [ ] Deploy V2 - Zero downtime deploy (Options: Docker swarm/Traefik/Bash script with Nginx reload (The latter seems the sanest solution for this project))

[RasmusKard]

https://semver.org/

[RasmusKard]

Zero downtime deploy workflow

1. Webhook on github repo, trigger on release (https://smee.io/)
2. Bash script to docker compose new container and use nginx reload to start routing users to new container (https://www.tines.com/blog/simple-zero-downtime-deploys-with-nginx-and-docker-compose/)
3. Kill old container