Release Process

[StuartFerguson]

Update release process as follows:

• On a push to the master/main branch a docker image is built and pushed to docker hub
• On pre-release create and tag docker image (this will not be released to the staging environment)
• On a non pre-release the staging environment will be updated

This change means that to test a change (end-to-end) the docker compose file will be used to spin up a dev environment. Is it possible this can be seeded as part of spinning up or does the seeding need done first time then stored on disk for reuse?

[StuartFerguson]

Issues Created