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
By default, fast_git_deploy never creates the symlink if you are doing a fresh deploy.
For already running apps, there's a task named 'deploy:warm' which runs mv releases releases.old and mv current current.old. I think moving them is safer than deleting them for existing deploys (You never want that "Oh shit...I broke my production app" feeling). With that said, you should always test your deploy script with deploy:warm on staging before doing it in a production env.
If you are really eager to clear up that current.old and releases.old, it's just one cap shell command away:
$ cap shell
cap> ls -al /my/current/path/current.old
cap> rm -rf /my/current/path/current.old
I'm exposed to
fast_git_deploy
for the 1st time while following Peepcode's Meet Chef.Yet I see in their example app that
deploy:symlink
is being overridden/removed since usingfast_git_deploy
renders it obsolete.How can this behaviour be integrated in
fast_git_deploy
instead?The text was updated successfully, but these errors were encountered: