aboutsummaryrefslogtreecommitdiff
path: root/op_guide
diff options
context:
space:
mode:
Diffstat (limited to 'op_guide')
-rw-r--r--op_guide/update_matrix.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/op_guide/update_matrix.md b/op_guide/update_matrix.md
index 27c12e0..16f6b33 100644
--- a/op_guide/update_matrix.md
+++ b/op_guide/update_matrix.md
@@ -80,8 +80,8 @@ If everythings worked as intended, you can commit and push your deployment file.
If something went wrong, you must rollback your deployment.
- 1. First, find a working deployment with [nomad job history](https://www.nomadproject.io/docs/commands/job/history)
- 2. Revert to this deployment with [nomad job revert](https://www.nomadproject.io/docs/commands/job/revert)
+ 1. First, find a working deployment with [nomad job history](https://www.nomadproject.io/docs/commands/job/history)
+ 2. Revert to this deployment with [nomad job revert](https://www.nomadproject.io/docs/commands/job/revert)
Now, if the deployment failed, you should probably investigate what went wrong offline.
In this case, I build a test stack with docker-compose in `app/integration` (for now, I had to do that only for plume and jitsi).