Deploy in an existing directory

[leopoiroux]

Hi Mike,
I made ​​a change for authorized to clone in a directory that already exists. This need appears if the directory is an NFS mount (with Vagrant for example). You can not remove this mount point :(
Thank you

[tamagokun]

can this be mkdir -p ?

[tamagokun]

If possible I would much prefer sticking with git clone, however I don't believe git allows you to clone into an existing repo.

For this to work we need to try and replicate everything that git clone would do:

From the manual:

Clones a repository into a newly created directory, creates remote-tracking branches for each branch in the cloned repository (visible
using git branch -r), and creates and checks out an initial branch that is forked from the cloned repository's currently active branch.

So rather than just adding the origin/default remote, it should get a list of the remote branches from the local repo and set it up that way.

[tamagokun]

A workaround would be to use $env->releases(true) in your config. This will use the current/releases/shared deploy style and will not try to nuke the folder on deploy.