As of today, we’re officially no longer supporting the very old Ruby 1.8, Python 2.5 and Python 2.6 programs on our servers. They’ll soon be removed from our servers entirely. (Ruby and Python are scripting languages; if you don’t know what they are, your site is unlikely to affected by this and you can ignore it.)
We’ve updated the default version of Ruby on Rails on our servers to version 2.2.3.
If you have a Ruby on Rails application that originally used Rails 1.1.6 or earlier, you might have trouble after yesterday’s Rails update (which also updated several other Ruby “gems”, including the “RubyGems” gem itself).
We’ve updated the default version of Ruby on Rails on our servers to version 2.1.0.
A heads-up if you use Ruby on Rails: We’re going to be upgrading the default version on our servers to 2.0.2 soon. We want to give you plenty of notice, because when we tried upgrading some older test applications, they didn’t work without changes.
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 126.96.36.199 to 188.8.131.52.
- 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.)
- PHP 7.1.28, 7.2.17 and 7.3.4
- Brief outage on web11 server March 20, 2019 (resolved)
- IPv6 enabled for new sites by default (and eventually for older sites, too)
- PHP 7.1.27, 7.2.16 and 7.3.3
- President’s Day 2019 holiday hours
- PHP 7.2.15 and 7.3.2
- Restore a full website, including all files and databases, with one click
- Brief MySQL scheduled maintenance February 8, 2019 (completed)
- Amazon Web Services (AWS) network problems January 16, 2019 (resolved)
- PHP 5.6.40, 7.1.26, 7.2.14 and 7.3.1