Before this latest release, I tried to publish a site using my usual end-of-development method: move the sites/foo.mydomain.com directory to sites/foo.com , and check settings.php for any necessary changes. I deleted the site's node in aegir, and started a verify on the platform so that it would pick up on the new site.... but it didn't. Verify completed successfully, the log indicates that aegir even picked up the modules and themes in sites/foo.com... but foo.com is not included in the sites list. I even went through and deleted the vhosts file for foo.mydomain.com to see if that would help, but no luck.
I could create a foo.com vhosts file and have the site work once DNS goes through... but I really want this site to be visible in Aegir. What can I do to make verify pick up on this new site again? Moreover, what should I do in future? I have several sites in development subdomains at the moment, how do I make them go live?
Thanks for a great tool, all. Really impressive work!
Comments
Maybe remove the drushrc.php
Maybe remove the drushrc.php file in the site's directory (at the same level as settings.php) and re-verify the Platform and see if that helps.
Note that since you didn't delete the site the normal way I presume, (Disable > Delete), there still maybe information about the site as it stood, in the hosting_site table... so you'll likely have some inconsistencies in the db, as your new site (if it imports) will have a different nid and you'll have the legacy stuff in the db still. Messy :/
This is off-topic to Aegir, but it feels wrong in my opinion to deploy to a 'live' site by renaming your development environment.. you really ought to keep both versions of the site running simultaneously and use proper version control to push changes between them. When your site goes live, all you're left with is a production site? Doesn't that seem risky to you?
Aegir is also not a build management tool so it's not design to handle this sort of thing. Or at least, things will actually be better if you run two versions of your site and push changes from dev > live through the standard methods. You could copy the site to foo.com and remove the drushrc.php of it, copy the database and make the settings.php changes, and then try and import the live site then. Or Clone the site (if you're running 0.4alpha1) to the new url, so that while the new site is a copy, it's unique as far as Aegir's concerned. Still not pretty but it will be a cleaner system and you'll have a dev version of your site remaining
Cheers
Interesting. Because of the
Interesting. Because of the way my clients operate (site upgrades like once every 3 years) I have no need for a development site for each client, once they've been deployed. I just keep a tar backup, and put the dev site live. When they do want redesign, or when I'm doing backend updates, I use subdomains to make sure each site is working... then rename the sites/whatever directories and change the basedir in apache.
So at present I have 3 platforms: aegir's private install of drupal 6.13, old sites on drupal 5.17 that I'm still migrating, production drupal 6.13, and the new drupal 6.14 I just set up today.
All of this is of course, subject to change now that I've started using Aegir. So, what sort of setup do YOU use for your deployment? What do you recommend? I'm running on a linode, so I have complete control.
and I just tried moving the
and I just tried moving the site over to the new drupal-6.14 platform by hand, and running the first verify on it. Doesn't show up. I removed drushrc.php from the sites/foo directory, I checked to make sure the site's drupal sql database is still there (that's why I deleted the node instead of a proper delete; I wanted to keep the site's sql db in place). Is there maybe somewhere internal to aegir or drush that is confusing this site with a previously deleted version of the same name?
Alternately, I'm not averse to wiping and completely reinstalling drush/aegir, particularly now that there's a new version out. I have plenty of CPU time to burn, so re-verifying everything would not be a big deal for me. But how do I remove aegir, now that it controls all my vhosts?
solution!
In case anyone else fracks themselves up like I did...
In the end I created a new site in Aegir, on my new drupal 6.14 platform. The site had the domain name of the production site I had "lost." that site created, installed and verified correctly. Then I just copied over everything from the real version of the site into that new site folder, except for drushrc. Maybe I could have copied drushrc; I just forgot. Anyway it all works now, thank the FSM.
Thanks for your help, mig5.
Same problem. Different fix.
I'm using the latest stable 0.3 and saw a similar issue. Here is how it happened:
site01.example.com was not imported after the verify.
I removed the drushrc.php corresponding to site01.example.com as mig5 suggested and reverified. Still not imported.
In Aegir I went to admin/content/node and found a node called site01.platform.com. When I visited this node the only tabs available were View, Edit, Delete (iirc). Couldn't tell whether this was the OLD site01 that didn't delete correctly, or the NEW site01 that didn't import correctly. I suspect the former because I never saw any messages indicating that the import was being attemped.
I manually deleted this node. Then I reverified platform01 and the new site01.example.com was correctly imported.
0.4 will probably solve these troubles. My step 3 is probably confusing Aegir somehow.