Bugs like #51 should not happen again in production as this tools is used by real people. This could have been avoided with a canary release.
Choose a subdomain for testing new versions with a small group of early adopters. beta.assistant.bloat.app?
Configure dns, nginx, certbot (outside of this repo)
Add a deploy script/option for the staging environment (how to include .env?)
The build system should add app version to the footer – from either git tag (if present) or commit hash (7 characters)
Bonus: the build system adds commit messages after the last tag in the current branch, so beta-testers always have up-to-date informtion on what has changed (and what they should try to break)
Bugs like #51 should not happen again in production as this tools is used by real people. This could have been avoided with a canary release.
beta.assistant.bloat.app
?.env
?)