Managing updates on your Pantheon (Mercury) Server

Events happening in the community are now at Drupal community events on www.drupal.org.
Posted by Greg Coit on October 13, 2010 at 4:37pm

There are many things to keep updated on any server and Pantheon is no exception. Fortunately, we've provided some tools to help.

To update the ubuntu packages, run update_mercury.sh

To update the pantheon/mercury files, run update_mercury.sh (yes, it does both)

To update pressflow, run update_pressflow.sh

To update Drupal modules, use drush's update module option.

Hope this helps,

Greg

Comments

Thanks!

Posted by vacilando on October 18, 2010 at 3:10pm

Thanks!

1) Is there a preferred order in which these updates should be applied?

2) What, in your opinion, is the appropriate frequency of running them?

3) I saw that the Ubuntu+Mercury update script (update_mercury.sh) is overwriting php.ini, thus removing customizations we had there (e.g. error_reporting etc.) Should these customizations be done elsewhere so as not to have to re-do them after running the update script?


---
Tomáš J. Fülöpp
http://twitter.com/vacilandois

3) It's recommended to make

Posted by jrstmartin on October 19, 2010 at 4:18am

3) It's recommended to make changes in /etc/mercury/server_tuneables. Copy/rename /etc/mercury/templates/tuneables to that location and check it out. You then apply your changes by running "bcfg2 -vqed".

There seems to be limited tweakability provided by server_tuneables. If you want to make a lot of changes, I think you would have to hack how Mercury/bcfg2 is baking the configuration files. You would possibly have to insert variables into a template config file that's being used by bcfg2? Then you would define those variables in server_tuneables? Maybe Greg can shed some light here?

Also see Greg's post on Mercury's template system.

Executing mercury_init via

Posted by jrstmartin on October 19, 2010 at 4:16am

Executing mercury_init via Hudson fails for me with "bzr: ERROR: Not a branch: "/var/www/"." because I run multiple sites out of separate directories, for example, /var/www/sitename.com/public_html/. Does Pantheon plan on supporting multiple site directories in the future? For now I just run update_mercury.sh separately.

re: Executing mercury_init via

Posted by Greg Coit on November 4, 2010 at 7:46pm

I think we're looking at supporting multiple site directories in the future, but it's not going to be in the next release (at least, not how you're using them - we are going to have dev, test and live site directories in the next version).

Unfortunately, any changes made to the files in /var/lib/bcfg2 will get overwritten when running update_pantheon. However, at this point, we're not expecting to push any updates to the 1.1 branch unless a security issue pops up.

Please do let us know if there are any variables in the php.ini files that you want to be able to configure.

Thanks!

Greg

--
Greg Coit
Systems Administrator
http://www.chapterthree.com

plus one

Posted by bewhy on April 4, 2011 at 2:31am

plus one on the dev, test and live directories

what you don't know will inspire you

How to update Drupal/Pressflow?

Posted by cookiesunshinex on January 6, 2011 at 9:40pm

This may sound like a silly question, but I just want to make sure that I'm doing everything correctly.

I have a Pantheon 1.1 AMI instance at Amazon.

I've been updating the site as necessary per your managing updates instructions above (thanks).

So now that Drupal 6.20 is out, to update Drupal from 6.19 to 6.20, do I run
$ sudo drush up

and then afterwards update Pressflow with
$ update_pressflow.sh

or do I only run $ update_pressflow.sh?

Sorry if this is really obvious. I have run many Drupal sites, but this is my first Pressflow site so I'm not sure of the procedure.

Thanks.

Symetrik Design
Drupal Consulting
http://www.symetrkdesign.com

re: How to update Drupal/Pressflow?

Posted by Greg Coit on January 7, 2011 at 6:44pm

Pressflow is modified version of Drupal and comes with everything one needs. So, you only need t update pressflow (via the update_pressflow.sh script).

If you install Drupal on a Pantheon server, it will break many of the caching mechanisms that Pantheon uses.

Hope this helps,

Greg

--
Greg Coit
Systems Administrator
http://www.chapterthree.com

Greg - I've got project

Posted by theatereleven on April 28, 2011 at 4:28pm

Greg - I've got project mercury up and running, but when I try and run one of the scripts mentioned above while logged into my server (SSH) it doesn't recognize it.

I'm on a Linode VPS. Could you shed light on this? THANKS.

Thanks for taking the time to

Posted by cookiesunshinex on January 7, 2011 at 8:29pm

Thanks for taking the time to respond Greg.

I understand what Pressflow is.

I'm just curious of what the best process for updating it.

So I should run the pressflow update first
$ sudo update_pressflow.sh

then run drush update to update any modules.
$ sudo drush up

The reason I'm asking is that I thought $ sudo drush up would also try to update core if core was reported to be out-of-date.
I did not know that drush was aware that pressflow was installed, but it apparently does.

Thanks.

Symetrik Design
Drupal Consulting
http://www.symetrkdesign.com

APT command failed

Posted by peterm95018 on June 28, 2011 at 8:28pm

I'm in the process of updating. I came back to this thread and ran the upgrade scripts for mercury and pressflow. When I login Ubuntu 10.04 is telling me I have a number of updates. I went to look at the update_mercury.log. Halfway through the log, I see an APT command failed entry.

The mercury_update reports that it completed successfully. However, I'm still getting the XX packages can be updated in the motd.

I'd like some advice on how to proceed. Should I just run apt-get update from the command line? Will I break Mercury config's in any way?

thanks,

Peter

First of all, check what

Posted by aleksey.tk on March 24, 2012 at 12:05am

First of all, check what usual apt-get update command gives you. If you receive any error saying that apt cannot download some package list - it means that you probably have karmic repositories setup in /etc/apt/sources.list.d, and karmic is now unsupported, just comment them out, and run update_mercury.sh again.

fixed

Posted by peterm95018 on March 27, 2012 at 4:09pm

Commenting out the karmic references in /etc/apt/sources.list.d/mercury.list and pantheon.list did the trick.

peterm

As now pressflow is on

Posted by aleksey.tk on November 21, 2012 at 1:53pm

As now pressflow is on github, update_pressflow.sh is now deprecated and will not work for you.

Mercury

Group organizers

Group categories

Post Type

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

AltStyle によって変換されたページ (->オリジナル) /