Posted by anarcat on May 4, 2009 at 8:33pm
Jump to:
| Project: | Provision |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
| Issue tags: | aegir-0.4 |
Issue Summary
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
#1
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...
#2
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
#3
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.
#4
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")) {#5
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.
#6
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.
#7
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.
#8