From 286ecce234c9a667e2f5b24c9f88413b2e1aca46 Mon Sep 17 00:00:00 2001 From: Mathieu Allaire Date: Thu, 9 Jul 2015 09:00:26 -0400 Subject: [PATCH] Update DEPLOYMENT.md --- DEPLOYMENT.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/DEPLOYMENT.md b/DEPLOYMENT.md index d10ecd66..c0971a41 100644 --- a/DEPLOYMENT.md +++ b/DEPLOYMENT.md @@ -76,8 +76,7 @@ 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 -to shutdown all the workers and re-exec itself to get your new code, which means -much higher waiting around for things to load. +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 from a Bundler context on start. This allows the cluster workers to load your app