Skip to content
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

Open
pearcec opened this issue Jul 12, 2012 · 9 comments
Open

Bundle drush-deploy #64

pearcec opened this issue Jul 12, 2012 · 9 comments
Assignees
Milestone

Comments

@pearcec
Copy link
Contributor

pearcec commented Jul 12, 2012

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.

@ghost ghost assigned dkingofpa Jul 12, 2012
@dkingofpa
Copy link

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.

@pearcec
Copy link
Contributor Author

pearcec commented Jul 12, 2012

I ran gem install drush-deploy. Then updated my local aliases to have these configs

  'remote-host' => 'localhost',
  'remote-user' => 'vagrant',
  'root' => '/srv/current/',

@pearcec
Copy link
Contributor Author

pearcec commented Jul 12, 2012

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?

@pearcec
Copy link
Contributor Author

pearcec commented Jul 12, 2012

I wonder if we can get the key forwarded some how for vagrant.

@pearcec
Copy link
Contributor Author

pearcec commented Jul 12, 2012

We can add the key

ssh-add /home/pearcec/.vagrant.d/insecure_private_key

That works.

@pearcec
Copy link
Contributor Author

pearcec commented Jul 12, 2012

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

@pearcec
Copy link
Contributor Author

pearcec commented Jul 13, 2012

@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.

@pearcec
Copy link
Contributor Author

pearcec commented Jul 13, 2012

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',
);

@pearcec
Copy link
Contributor Author

pearcec commented Jul 13, 2012

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants