Open pearcec opened 12 years ago
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
'remote-host' => 'localhost',
'remote-user' => 'vagrant',
'root' => '/srv/current/',
It fails.
** [deploy:update_code] exception while rolling back: Capistrano::ConnectionError, connection failed for: vagrant@localhost (Net::SSH::AuthenticationFailed: vagrant)
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
* executing "cd /srv/releases && tar xzf /tmp/20120712191530.tar.gz && rm /tmp/20120712191530.tar.gz"
servers: ["localhost"]
[vagrant@localhost] executing command
*** [err :: vagrant@localhost]
*** [err :: vagrant@localhost] gzip:
*** [err :: vagrant@localhost] stdin: unexpected end of file
*** [err :: vagrant@localhost] tar: Child returned status 1
*** [err :: vagrant@localhost] tar: Exiting with failure status due to previous errors
command finished in 9ms
*** [deploy:update_code] rolling back
@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:
<?php
$databases['default']['default'] = array(
'driver' => 'mysql',
'database' => 'drupal',
'username' => 'username',
'password' => 'password',
);
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.