Right now, provision completely ignores the 'default' site, which is rather problematic especially if you want to upgrade that site. We should treat that site as any other, except maybe for anything that touches hostnames (DNS and Apache vhost). The exceptions should sit there.

Comments

anarcat’s picture

I have tried to migrate my Aegir install into sites/hostmaster.koumbit.net here. I had to change my cron job to add the --uri=hostmaster.koumbit.net argument.

Update: obviously, that doesn't work because then all drush hosting commands need to be fixed...

adrian’s picture

Status: Active » Fixed

Hosting setup is now re-runnable.

the only exception is that the master site shouldn't be imported into it's own data store.

http://drupal.org/node/454312#comment-1635306

anarcat’s picture

Version: 5.x-0.2-alpha1 »
Status: Fixed » Needs work

So right now, drush + provision HEAD do not import the site in sites/default. Since this is general the case of sites we have to import into Aegir here (most sites are single-site installs we want to migrated in a big multi-site), this is a major annoyance, so I'm reopening this.

The idea here is to stop ignoring the site in sites/default.

anarcat’s picture

Priority: Normal » Critical
Status: Needs work » Needs review

This is a one-line change... should we package this in 0.3?

./platform/provision_drupal.drush.inc:322:        if (file_exists("$file") && ($subdir != 'default') && !is_link("./sites/$subdir")) {
adrian’s picture

Priority: Critical » Normal
Issue tags: +aegir-0.4

the reason we don't import default is because we have no way to determine the url for it, hence we have no way to determine how to generate the virtual host file.

additionally you can have a 'default' on every platform, so this is really not a one line fix. it requires a refactor and additional database fields and modification of the table constraints and validation.

this is not an 0.3 thing.

adrian’s picture

the reason we don't import default is because we have no way to determine the url for it, hence we have no way to determine how to generate the virtual host file.

additionally you can have a 'default' on every platform, so this is really not a one line fix. it requires a refactor and additional database fields and modification of the table constraints and validation.

this is not an 0.3 thing.

adrian’s picture

Status: Needs review » Needs work

obviously anything from way back then doesn't apply.

i still dont think this can be done realistically, we simply do not know enough about the site to be able to import it. and we cant have a million sites called 'default' hanging around.

it really is not that hard to move the directory, so it should really be a documentation issue.

Steven Jones’s picture

Version: » 6.x-1.x-dev
Component: Code » Documentation
Steven Jones’s picture

Version: 6.x-1.x-dev » 6.x-2.x-dev
Component: Documentation » Code
Category: task » feature
Issue tags: -aegir-0.4

This came up again and again today at Drupalcon, and I'm going to tentatively mark this back as code rather than documentation task. We should see if we could support using the default folder for sites, because there are a lot of people who use that setup. It would also ease the pain of people getting into Drupal.

chrowe’s picture

I would also like this feature since I work with Aegir as a development tool on projects where the live site is in sites/default and other developers used that setup as well. Would it be possible to only allow it via drush and require a url parameter and whatever else is needed?

ergonlogic’s picture

Version: 6.x-2.x-dev » 7.x-3.x-dev
Issue summary: View changes

New features need to be implemented in Aegir 3.x, then we can consider back-porting to Aegir 2.x.