From ecc40c7ea3edcb526e77a93cf164bd7c72fb924f Mon Sep 17 00:00:00 2001 From: Trevor Turk Date: Thu, 3 Mar 2016 10:36:39 -0600 Subject: [PATCH] Checks doc: example for setting DOKKU_DEFAULT_CHECKS_WAIT for a single app --- docs/checks-examples.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/checks-examples.md b/docs/checks-examples.md index ab675965c..93e711de3 100644 --- a/docs/checks-examples.md +++ b/docs/checks-examples.md @@ -6,10 +6,11 @@ checks:disable checks:enable Enable zero-downtime checks ``` -Following a deploy, dokku will now wait `10` seconds before routing traffic to the new container. If the container is not running after this time, then the deploy is failed and your old container will continue serving traffic. You can modify this value using the following command: +Following a deploy, dokku will now wait `10` seconds before routing traffic to the new container. If the container is not running after this time, then the deploy is failed and your old container will continue serving traffic. You can modify this value globally or on a per-application basis: ```shell dokku config:set --global DOKKU_DEFAULT_CHECKS_WAIT=30 +dokku config:set DOKKU_DEFAULT_CHECKS_WAIT=30 ``` If your application needs a longer period to boot up - perhaps to load data into memory, or because of slow boot time - you may also use dokku's `checks` functionality to more precisely check whether an application can serve traffic or not.