You are currently browsing the Brightbox Blog weblog archives for June, 2010
We’ve built new 32 & 64bit Ruby Enterprise 1.8.7-2010.02 packages for Ubuntu Hardy and Lucid. The 2010.02 release of Ruby EE includes a number of backported fixes for critical bugs in Ruby 1.8.7p249 and we recommend users currently using our 2010.01 packages upgrade immediately.
For further information on using these packages see the release announcement for our Ruby EE 2010.01 packages.
Available from today, you can now choose either Ubuntu Hardy or Lucid as the base OS when building new Brightboxes.
Ubuntu Lucid is the latest Long Term Support (LTS) version of Ubuntu with security fixes provided until April 2015. It brings a whole bunch of upgrades such as Ruby 1.8.7, Monit 5, Apache 2.2.14 and new packages like CouchDB, Sphinx, Chef, RabbitMQ, MongoDB, ejabberd and many more.
We’ve treated it to the usual Brightbox Ruby deployment tune-up, including our Ruby Enterprise Edition 1.8.7-2010.01 packages. Updated Phusion Passenger packages are now available on our newly Lucid-enabled apt repository.
When buying a new Brightbox, you’ll see a combo box that you can use to select Lucid (Hardy is still currently the default). Upgrading from Hardy to Lucid isn’t really viable due to the way Hardy boxes handle kernels, so you’ll either need to request a re-image (which involves wiping your box, so make backups!) or buy a new box and move your apps to it.
Getting access to your newly purchased Brightboxes used to require a trip to the control panel to retrieve the ‘rails’ user password. If you’re using config management systems like Chef or Puppet this is likely the only laborious aspects of configuring your box. No longer!
Now, whenever a new box is deployed, the SSH keys of all the technical contacts on your Brightbox account are automatically pre-installed for the default ‘rails’ user. To add your own SSH key, edit your user profile within the control panel and paste in your SSH public key using the editor at the bottom.
Remember, this only affects newly provisioned boxes – as the it’s done during the box build stage. Removing or adding technical contacts in the control panel at a later date will not automatically change any access control on existing boxes.
