Heretofore I've been wiping away my test installation and re-installing each time I grab a new version from HEAD. What would be the best way to upgrade an existing site, though? Assuming a point release, or even just the dev version I suppose.

Starting this issue to add to documentation as well.

Comments

drupalninja99’s picture

Status: Active » Needs review

For a normal user upgrading I would say they would just remove the openchurch profile and re-download the profile, then run drush updatedb (in a test environment).

But since you are kind of a beta tester its not a bad idea for you to just do the following:

1. Wipe out your openchurch docroot
2. Do drush dl openchurch, select version
3. Edit your settings.php file
4. Make your sites/default/files writable
5. Run drush si -y openchurch

I do this kinda, but with a drush make file so that I can get the latest dev version before the packager has packaged it. I actually put this commands into a bash script called build_openchurch.sh so as to make things quicker. So if you had a bash script that would help you be able to run a new version fairly quickly.

I wish I could just do drush up openchurch to change out the whole openchurch profile but I don't believe that functionality exists (yet).

drupalninja99’s picture

ok good news. I just finished watching the drush 5 drupalcon presentation and now there is a new 'quick drupal' command that lets you install drupal or any install profile in 1 easy command.

I will do some testing, but it is really slick. Drush 5 has its own web server.

And so the command would be something like "drush qd openchurch_demo --core=openchurch --profile=openchurch" - something like that. I haven't downloaded drush 5 but this will really help things as far as testing goes.

If you need to get a fresh copy of dev before the Drupal.org packager has built it you would still want to write a bash script to run a drush make command and run the installer. I have to do that often since I am trying to verify pretty quickly whether a change I've made has worked. But the dev packager I think runs every few hours so that may not be an issue for you when you're testing.

drupalninja99’s picture

(dup comment)

StephenBrown’s picture

That would be cool indeed. I was going to say that the download for openchurch currently isn't just the install profile, it's the whole shebang, with core and everything, so I don't know how well that would work for a normal user. (Aside from copying out the sites directory, replacing the rest of it, and replacing the sites directory.) Also that means that modules will need to be updated separately... and such.

quick-drupal looks quite cool, and there's a PPA for Ubuntu with PHP 5.4 in it, so I'm eager to get that upgraded and try it out myself.

StephenBrown’s picture

I'd also recommend you check out the topic pages for drush (run 'drush topic') to find out a lot more about what's new in drush 5. For one, it looks like there are 15-20 new commands in core (Especially drush make. Perfect for you!) Very exciting stuff.

drupalninja99’s picture

I was having a lot of problems with getting the drush server to work bc I dont have php 5.4 or php cgi. It doesn't appear that many Drupal stacks do.

StephenBrown’s picture

True. It is quite new, though I've found a few places to get it for Linux (which as usual is better supported).
Though even the Drupal Community is debating on whether it should be required: http://drupal.org/node/1498574

For CentOS 6: http://www.webtatic.com/packages/php54/
For Ubuntu 11.10/12.04: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-php54 and http://apt.damz.org/

Unfortunately I haven't looked for Mac or Windows packages.

dbt102’s picture

Do you really think the normal user upgrading knows how to use drush?

I just ran update from admin menu ( Appearance \ Update ) which completed OK.

It weird though, block (per Home » Administration » Structure » Blocks) show all blocks are disabled. But the site looks OK after clearing caches.

drupalninja99’s picture

No these instructions are namely for testers who have to download and install OC a lot to verify functionality.

You don't want to run update bc it will change the codebase of OC to something that is untested. If you do make those updates, you will want to test on a local/test environment first.

drupalninja99’s picture

Status: Needs review » Fixed

Going to close.

Status: Fixed » Closed (fixed)

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

drupalninja99’s picture

Issue tags: +Documentation

Tagging as documentation