-
Notifications
You must be signed in to change notification settings - Fork 11
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
Bundle drush-deploy #64
Comments
I'd prefer to bundle it when the project reaches 2.0. That's when the name-change will happen. We'll circle back around on this issue. |
I ran gem install drush-deploy. Then updated my local aliases to have these configs
|
It fails.
Need to figure out how to get access to the vagrant private key? |
I wonder if we can get the key forwarded some how for vagrant. |
We can add the key ssh-add /home/pearcec/.vagrant.d/insecure_private_key That works. |
Still failed
|
@dkingofpa I agree we can wait. In the meantime it is easy enough to add it yourself. Unfortunately I am still running into issues with it. |
One of the things I had to do was add the database.php to the srv/ directory. It looks like this:
|
Something else that doesn't work very nice is the fact the symbolic link for current is the full path in vagrant under virtualbox. We might need to override the cap task to make it relative. |
I would like to see us bundle drush-deploy. That way we can run
drush-deploy SCM=none REPO=. TARGET=local inside vagrant to set our distro.make file changes.
The text was updated successfully, but these errors were encountered: