You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've just run into problems, while having the to :launch block inside the do deploy block all commands where not executed after deploy in the launch phase, they where instead executed in the deploy phase. Which might also explain why others had problems launching stuff in the final current_path...
So I've changed it like this:
deploy do
invoke :'git:clone'
[...]
invoke :'deploy:cleanup'
end
to :launch do
Maybe the docs don't reflect the latest version or I've done completely wrong. Maybe someone can have a look at this.
Also using to :prepare outside/before the deploy do block helped, so I was able to stop delayed_job proper from the current app directory.
Hope this helps.
Cheers,
Alexander
The text was updated successfully, but these errors were encountered:
Hmm, when you're using the prepare block you need to add default block for the default invokes (clone, bundle, migrate...). Besides that, everything else need to work out of the box, did you add
Hello,
I've just run into problems, while having the to :launch block inside the do deploy block all commands where not executed after deploy in the launch phase, they where instead executed in the deploy phase. Which might also explain why others had problems launching stuff in the final current_path...
So I've changed it like this:
[...]
Maybe the docs don't reflect the latest version or I've done completely wrong. Maybe someone can have a look at this.
Also using to :prepare outside/before the deploy do block helped, so I was able to stop delayed_job proper from the current app directory.
Hope this helps.
Cheers,
Alexander
The text was updated successfully, but these errors were encountered: