Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

to :launch ... #261

Closed
finger-berlin opened this issue Dec 5, 2014 · 1 comment
Closed

to :launch ... #261

finger-berlin opened this issue Dec 5, 2014 · 1 comment

Comments

@finger-berlin
Copy link

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:

  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

@gabskoro
Copy link
Member

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

cd #{deploy_to}/#{current_path}

Before stopping, starting delayed job?

@d4be4st d4be4st closed this as completed Jul 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants