nesquena / cap-recipes Goto Github PK

it seems to me it should be targeted to the :app role, is setting it to :web a mistake or intentional?

Hi Nathan,
thx for these very handy recipes.
I use capistrano-ext [https://github.com/jamis/capistrano-ext] to manage my stage environments.

I had to monkey patch one of the rail recipes to handle this case.

namespace :rails do
  desc "Displays the stage (production, staging or whatever) log from the server locally"
  task :tail, :roles => :app do
    stream "tail -f #{shared_path}/log/#{stage || "production"}.log"
  end
end

Now the task serve me the right log file depending on my configuration.
I thought it could be a good feature for this gem.

If you think so too, I can request a pull from you to implement this (in others tasks too...).

It will be very nice to have receipt to run Resque workers via Capistrano.

Hi there!
I'm trying to use the Juggernaut Recipe but every time that I deploy the capistrano gets stuck with the juggernaut session. I think that should start juggernaut's session in background but this is not happening.

The log says that all the commands were executed and so get stucks on line like this :

25 Jun 21:29:36 - socket.io ready - accepting connections

Any thoughs ?!

Thanks for the attention.

How can there not be any padrino specific recipes?