Update templates (#176)(patch)

Update instructions for using the housekeeper containers

.github/PULL_REQUEST_TEMPLATE

@@ -16,9 +16,14 @@
 
 ### How to prepare for test
 
-- [ ] ssh to hasta (depending on type of change)
-- [ ] install on stage:
-```bash /home/proj/production/servers/resources/hasta.scilifelab.se/update-tool-stage.sh -e S_cg -t housekeeper -b YOURBRANCH```
+- [ ] ssh to Hasta
+- [ ] Test your branch with
+
+```bash
+housekeeper-test-deploy <branch-name>
+housekeeper-test <command here>
+```
+Any migrations need to be applied manually with alembic against the stage database.
 
 ### How to test
 - [ ] login to ...

DEPLOYMENT.md

@@ -2,18 +2,16 @@
 This includes instructions for deploying Houskeeper in the Clinical Genomics :hospital: setting. General instructions for deployment is in the [development guide][development-guide]
 
 ## Steps
-When all tests done and successful and PR is approved by codeowners, follow these steps:
+When all tests are done and successful and the PR is approved by codeowners, follow these steps:
 
 1. Select "Squash and merge" to merge branch into default branch (master/main).
 2. Append version increment value `( major | minor | patch )` in the commit message to specify what kind of release is to be created.
 3. Review the details and merge the branch into master.
-4. Deploy in stage on Hasta:
-    - `us`
-    - `bash /home/proj/production/servers/resources/hasta.scilifelab.se/update-tool-stage.sh -e S_cg -t housekeeper -b master`
-5. Deploy in production by running the following commands:
-    - `down`
-    - `up`
-    - `bash /home/proj/production/servers/resources/hasta.scilifelab.se/update-tool-prod.sh -e P_cg -t housekeeper -b master`
+4. Deploy the latest version to stage and production with `housekeeper-deploy`.
+5. Apply any migrations against the stage and prod databases with alembic.
+    - Ensure that you have the latest revisions in your branch.
+    - Ensure that you have the correct tunnels open against Hasta.
+    - Ensure that you point to the correct alembic config when you apply the revisions with `alembic --config <config path>` upgrade head`
 6. Take a screenshot or copy log text and post as a comment on the PR. Screenshot should include environment and that it succeeded.
 7. Great job :whale2: