Hello, I've installed and setup Aegir as described in the INSTALL.txt and I can't complete the install wizard. I'm very close.

I can't run the "hosting setup" command. I'm running Ubuntu 8.04

The final steps of the setup instruct me to run these commands as aegir user:
cd /var/aegir/drupal-5.x
/var/aegir/drush hosting setup

I get this reponse:
bash: /var/aegir/drush: is a directory

I would expect this from these commands in the INSTALL.txt
cd /var/aegir
cvs co -d drush contributions/modules/drush

I run /var/aegir/drush/drush.php hosting setup and get this response:
php '/var/aegir/drush' hosting dispatch --root='/var/aegir/drupal-5.x'Dispatch command could not be run.

I run /var/aegir/drush/drush.php help and see the hosting and provision commands.

What's a guy to do? What did I miss?

Mike

Comments

adrian’s picture

adrian commented
Status: Active » Fixed

You are asked to specify the COMPLETE path to the drush.php file, including the php file itself.

hence /var/aegir/drush/drush.php

change the setting in the wizard, and it will show you the correct command to run in the initialize step

MichaelCole’s picture

MichaelCole commented

Nice! Exactly what needed to be done.

Adding drush.php to the string might make a better default. Save on other people running into it in the future.

Thanks Adrian!

Mike

adrian’s picture

adrian commented

We can't actually default it to anything, because we have no way of knowing where drush.php has been stored.

it could also be a symlink and it could also be an alias and it can also be in the path, which is why we ask for the full path to drush.php

anarcat’s picture

anarcat commented

We could try to lookup drush in a few key locations (~/drush/drush.php, `whereis drush.php`, `whereis drush`...).

kanani’s picture

kanani commented

I put a symlink into /usr/sbin/

and then didn't need to specify full path to get "Dispatch command was run successfully"

Now if I could just get rid of that pesky "Could not connect to master database error"

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.