Software updates: Ruby on Rails, phpMyAdmin, WordPress

We’ve updated several things on our servers today:

  • Ruby on Rails was updated from version 1.2.3 to 1.2.6. (If you use Rails on your site, our page explaining how to freeze Rails explains how you can get total control of Rails updates.)
  • phpMyAdmin was updated from version 2.11.2.1 to 2.11.2.2.
  • The WordPress software that runs this blog was updated to version 2.3.1. That doesn’t directly affect our customers — but if you’ve installed your own version of WordPress on your own site, this is a good reminder to update it: some older versions have security vulnerabilities. (We found that the update from 2.2.X to 2.3.1 was painless.)

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a comment on the bottom of this page.

4 Comments so far

  1. Do you really have a copy of Wordpress developed in Ruby? Or am I not reading the blog post properly? That is pretty cool if it is. Anyways, nice blog you have going on here. Nice SEO work too.

    Jenn

  2. While a Ruby on Rails version of WordPress would be pretty cool, unfortunately these were three separate software updates that were done at the same time and therefore got announced in a single blog post. Our apologies that that wasn’t more clear — perhaps we should do separate posts for separate programs, even if they’re updated at the same time.

  3. hi — not exactly a ruby question, but –

    on your support page it says you are running python 2.3.5, which is rather old and i’m assuming you probably have python 2.5 installed. is that true? is it possible to run a pylons (or other python app server) behind fastcgi?

  4. We have Python 2.3.5 and 2.4.1 available, but not 2.5 yet (that will happen when we do our next major Debian Linux upgrade later this year). Regarding pylons — good question! We haven’t had any feedback from any customers who have tried it. In theory it should work, but we can’t say for sure until someone tries it, or until we get some time to experiment with it.

Add a comment

Fields in bold are required. Email addresses are never published or distributed.

Some HTML code is allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
URIs must be fully qualified (eg: http://www.domainname.com) and all tags must be properly closed.

Line breaks and paragraphs are automatically converted.

Please keep comments relevant. Off-topic, offensive or inappropriate comments may be edited or removed.