From 25bd4c878513cbbd0ffba9c87d96091b1dab6993 Mon Sep 17 00:00:00 2001 From: Sherman K Date: Fri, 19 Jan 2018 00:34:39 +0800 Subject: [PATCH] Update relevant docs with ps:stopall --- docs/deployment/process-management.md | 7 +++++++ docs/development/plugin-triggers.md | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/deployment/process-management.md b/docs/deployment/process-management.md index db31b020d..3e8884a75 100644 --- a/docs/deployment/process-management.md +++ b/docs/deployment/process-management.md @@ -14,6 +14,7 @@ ps:scale = [=] # Get/Set how many instances of a ps:set-restart-policy # Sets app restart-policy ps:start # Start app container(s) ps:stop # Stop app container(s) +ps:stopall # Stop all app container(s) ``` By default, Dokku will only start a single `web` process - if defined - though process scaling can be managed by the `ps` plugin or [via a custom `DOKKU_SCALE` file](/docs/deployment/process-management.md#manually-managing-process-scaling). @@ -99,6 +100,12 @@ Deployed applications can be stopped using the `ps:stop` command. This turns off dokku ps:stop node-js-app ``` +You may also stop all applications at once: + +```shell +dokku ps:stopall +``` + ### Starting applications All stopped containers can be started using the `ps:start` command. This is similar to running `ps:restart`, except no action will be taken if the application containers are running. diff --git a/docs/development/plugin-triggers.md b/docs/development/plugin-triggers.md index c5d947c54..9081eb446 100644 --- a/docs/development/plugin-triggers.md +++ b/docs/development/plugin-triggers.md @@ -744,7 +744,7 @@ verify_app_name "$APP" ### `post-stop` - Description: Can be used to run commands after an application is manually stopped -- Invoked by: `dokku ps:stop` +- Invoked by: `dokku ps:stop` and `dokku ps:stopall` - Arguments: `$APP` - Example: