-
Notifications
You must be signed in to change notification settings - Fork 0
Deployment
Bogdan Marc edited this page Sep 9, 2024
·
2 revisions
The detailed deployment mapping is described in deployment.yml
. At the time of
writing, using the new infrastructure, the deployment process is as follows:
- commits to the
dev-infrastructure
branch will deploy thedev
server - commits to the
preprod
branch will deploy thepre-production
server - any commit on the
prod
branch will deploy theproduction
server as a new release
If the commit is a "new" release, the deployment should be tagged with the same
version number, e.g. 1.2.3
. as set in the /app/lib/version.rb
and a short
annotation summarising the updates should be included in the tag.
Once the production deployment has been completed and verified, please create a
release on the repository using the same latest version number. Utilise the
Generate release notes from commit log
option to create specific notes on the
contained changes as well as the ability to diff agains the previous version.
- There is a workaround to removing the PID lock of the Rails process in the event of the application crashing and not releasing the process.
- The rails
SECRET_KEY_BASE
is created here.