aboutsummaryrefslogtreecommitdiff
path: root/op_guide
diff options
context:
space:
mode:
authorQuentin <quentin@deuxfleurs.fr>2020-11-22 13:01:05 +0100
committerQuentin <quentin@deuxfleurs.fr>2020-11-22 13:01:05 +0100
commitcfab2346cf075d4c470f52761f6f6066a34e5ea6 (patch)
tree29554fc3c37032d338a7d8c20764d35bd106eb0a /op_guide
parentf544c202be50ec8cbbd0e7cbfbada63f881081da (diff)
downloadinfrastructure-cfab2346cf075d4c470f52761f6f6066a34e5ea6.tar.gz
infrastructure-cfab2346cf075d4c470f52761f6f6066a34e5ea6.zip
Another another try
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).