From fd5e093e35a1295d181323098965d66d7bf9cbc8 Mon Sep 17 00:00:00 2001 From: KID the Euforia Date: Wed, 14 Jul 2021 10:54:54 +0900 Subject: [PATCH] `preload!` -> `preload_app!` in docs/deployment.md Signed-off-by: KID the Euforia --- docs/deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/deployment.md b/docs/deployment.md index 64b236dbe6..f80bf42b0a 100644 --- a/docs/deployment.md +++ b/docs/deployment.md @@ -100,7 +100,7 @@ You probably will want to deploy some new code at some point, and you'd like puma to start running that new code. Minimizing the amount of time the server is unavailable would be nice as well. Here's how to do it: -1. Don't use `preload!`. This dirties the master process and means it will have +1. Don't use `preload_app!`. This dirties the master process and means it will have to shutdown all the workers and re-exec itself to get your new code. It is not compatible with phased-restart and `prune_bundler` as well. 1. Use `prune_bundler`. This makes it so that the cluster master will detach itself