During launch stage, current symlink points to previous release

[edwardmp]

I want to run some commands in the launch stage.
But I noticed current_path location points to the the previous deployment..
Of course I want to run something in the current deploy directory.
Is there another stage than launch I can use for this?

Same issue as here:
http://stackoverflow.com/questions/19836302/mina-deployment-invoke-task-once-current-symlink-is-updated

[gabskoro]

Hi,

Launch is called after the new app folder was symlinked, so if you want to restart your server you need to replace this

queue! %[bundle exec thin restart -C "#{thin_yml}"]

with

queue %["cd #{deploy_to}/#{current_path} && bundle exec thin restart -C #{thin_yml}"]

[13k]

what if I want to run stuff (for example: notifications, tracking metrics) before the launch stage and want to use the latest (HEAD) code?

[13k]

nevermind, I realized the current, unchanged, directory it's the actual (temp) build directory

[edwardmp]

I am still having this issue. For example, I run a database migration on :launch, but it is only committed after the second mina deploy. The current symlink still refers to the old when :launch is triggered