workflow for rollout day has been defined
Workflow for rollout day
--> announce some days before <--
--> because no access will be possible on this day <--
- stop REST service
- pull rollout_branch
(git pull; git checkout roll_out) - do changes to database schema
- if updates on extension are needed: see https://gitlab.version.fz-juelich.de/toar/toardb_fastapi/-/issues/3#note_51339
This -- of course -- has to be done on the database machine (zam10116/zam10131).
First copy toar_controlled_vocabulary--0.1.sql to its appropriate place, then continue with the installation. - full database reset: delete (or first rename then delete after completion of this step) complete database, install from scratch (see README.md, use database schema (toardb_v2_schema.sql) from repository), and upload/adapt data
- incremental database changes: run psql-script (db_changes.psql -- see #22 (closed)) with changes made to the database structure since last rollout
- if updates on extension are needed: see https://gitlab.version.fz-juelich.de/toar/toardb_fastapi/-/issues/3#note_51339
- check new software and database on local port of join-dev
- pytests
- live tests
- eventually (from tests): additional fixes to
- toardb_v2_schema.sql (do not forget to also update toardb_v2_dump.sql -- for easier testing on a small database (not the productive one))
- software
- merge rollout_branch to master on gitlab
- check documentation (later: replace in TOAR Data Centre)
- start REST service
- live tests (see above (4), but on production port)
- eventually (from productive live tests): repeat steps 5 to 7 (now directly pushing to master)
- inform the group about changes since the last rollout and that service is available again