From aabe456aa6644e954b8ee9583c8dd536f1454b21 Mon Sep 17 00:00:00 2001 From: Trevor Turk Date: Thu, 3 Mar 2016 10:41:42 -0600 Subject: [PATCH] Checks doc: example for setting DOKKU_WAIT_TO_RETIRE 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 ec65ce599..6c65bc87c 100644 --- a/docs/checks-examples.md +++ b/docs/checks-examples.md @@ -13,10 +13,11 @@ dokku config:set --global DOKKU_DEFAULT_CHECKS_WAIT=30 dokku config:set DOKKU_DEFAULT_CHECKS_WAIT=30 ``` -Dokku will wait `60` seconds before stopping the old container so that existing connections are given a chance to complete. This value is also configurable globally: +Dokku will wait `60` seconds before stopping the old container so that existing connections are given a chance to complete. You can modify this value globally or on a per-application basis: ```shell dokku config:set --global DOKKU_WAIT_TO_RETIRE=120 +dokku config:set DOKKU_WAIT_TO_RETIRE=120 ``` > Note that during this time, multiple containers may be running on your server, which can be an issue for memory-hungry applications on memory-constrained servers.