I must not be the only one who occasionally wants to stop a Ruby on Rails application. There are long-running and risky database schema migrations and data migrations, and you don’t want users fiddling the system in the middle of the deployment. With a Mongrel-based setup it was easy to set up a 503 (Service unavailable) error page and then just shut down all the Mongrels, so that Apache could giv
![Stopping your Rails application with Phusion Passenger - The CA Flowdock Blog](https://cdn-ak-scissors.b.st-hatena.com/image/square/74cd89060168b3e35ca942d7ceb333a2d35f58d4/height=288;version=1;width=512/http%3A%2F%2Fblog.flowdock.com%2Fwp-content%2Fuploads%2F2014%2F11%2Fflowdock_logo_square.png)