forked from Deuxfleurs/infrastructure
Another another try
This commit is contained in:
parent
f544c202be
commit
cfab2346cf
1 changed files with 2 additions and 2 deletions
|
@ -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.
|
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)
|
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)
|
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.
|
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).
|
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).
|
||||||
|
|
Loading…
Reference in a new issue