prune_bundler option to be default about capistrano-puma

[seuros]

set :puma_prune_bundler, true in your deploy.rb
then run puma:config to regenerate the puma.rb

[sime]

Cheers.

On Mon, Nov 17, 2014 at 11:49 PM, Abdelkader Boudih <
[email protected]> wrote:

Closed #82 #82.

—
Reply to this email directly or view it on GitHub
#82 (comment).

[sime]

This issue is still chasing me. Manage to break the app after a sprockets upgrade that wasn't noticed by puma. My puma.rb is as follows:

#!/usr/bin/env puma

directory '/home/staging/site/current'
rackup "/home/staging/site/current/config.ru"
environment 'staging'

pidfile "/home/staging/site/shared/tmp/pids/puma.pid"
state_path "/home/staging/site/shared/tmp/pids/puma.state"
stdout_redirect '/home/staging/site/shared/log/puma_access.log', '/home/staging/site/shared/log/puma_error.log', true

threads 0,16

bind 'unix:///home/staging/site/shared/tmp/sockets/puma.sock'
workers 0

prune_bundler

[sime]

And every 5th release I have to start puma manually.