the-red-button | Red Button enables you to quickly put

Configure your Nginx vhosts using the files supplied in the nginx/ directory and reload your Nginx configuration. Make a maintenance.html page (if you don’t already have one) and place it in your application’s public/ folder.
Configure your Nginx vhosts using the files supplied in the nginx/ directory and reload your Nginx configuration. **Make sure the _maintenance.include file is placed at the end of each vhost to prevent conflicts with other rewrite rules.**
Make a maintenance.html page (if you don’t already have one) and place it in your application’s public/ folder.
Add a symlink in your application’s public directory to the location where your Panic script will put the "maintenance-on" file for that target. Your shared/ directory is a good choice: ln -s /var/www/example.com/shared/maintenance-on /your/application/public/ The Nginx rewrite rule only works if the symlink resolves to an actual file. Putting the maintenance-on file in shared/ means your maintenance page will remain up between deploys until the maintenance-on file is either deleted manually or using a Capistrano task. If you don't want this behavior, then you can skip this step and just configure public/ as the directory for your targets. Targets configured in this manner will not have persistent maintenance pages and will become active again when new code is deployed.
Modify the panic.rb script and add your targets.
Wait until it is time. Hopefully you’ll never have to push The Red Button, but now you are ready to panic.