Turnkey Rails 2.3.2 Now Available


Ruby on Rails 2.3.2

We are pleased to announce the availability of the Ruby on Rails 2.3 stack (currently 2.3.2, as of this writing).

We have opted to try out the excellent (Ubuntu-based) Turnkey Linux software appliance for Rails 2.3, rather than using our own installation and provisioning scripts, and so far we have had excellent results.

(We have also had good results with the Turnkey Drupal appliance as well).

Things we liked about the Turnkey appliance:

  • Preconfigured SSL / SSH support – all keys & certs  generated during installation, set up w/Apache
  • Security-related updates applied daily
  • Webmin preinstalled and precofigured for Apache, MySql, etc
  • RubyGems package manager installed the way we recommend – with Ruby managed by apt, but Gems installed from source.
  • Just as we say: “Use gem for managing Rails gems, and apt for everything else.”

Things we had trouble with or had to fix:

  • The 3-node mongrel cluster was cumbersome to administer, and difficult to modify for new rails apps from the “Example” rails app preinstalled by Turnkey.  Either No example app, or a more flexible way to add new apps would have been better.
  • No option for, or mention of Phusion Passenger.
  • SQLite and git were not installed
  • Our regular VMs do a reconfigure tzdata on first startup, so you don’t forget to set your timsezone correctly

Additional notes and packages we installed:

  • mc – Midnight Commander – tried-n-true text mode dual-pane file manager
  • file – Without this, obscure dependencies remain unmet for builds, etc
  • sqlite3, libsqlite3-ruby – should be installed, even if MySql is the default db (Postgres might be nice too)
  • git-core should be installed, given the percentage if Rails plugins that use it, plus gems can install from git, but only if it’s installed!
  • lynx, other viewers for mc – important for reading docs in console
/etc/init.d/mongrel_cluster stop

didn’t work, and had to manually stop the clusters on ports 8000, 8001, & 8002

Had to manually do things like:

mkdir -p tmp/pids


chown -R www-data:www-data *

on certain directories, etc, to make certain core components work, that shouldn’t have been necessary.

Anyway, these considerations are relatively minor, and are all addressed now, and working well – just select “Rails 2.3”  from the dropdown when you place your order –

Plus, look for a future update where we integrate Phusion Passeneger with your VM – Let us know what you prefer, please enter which deployment option you prefer for Rails in the comments on this post, and why –

  • Mongrel, Mongrel cluster
  • Phusion Passenger/mod_rails
  • mod_wsgi
  • Apache
  • nginx
  • Lighttpd
  • etc

…and we’ll listen!


Leave a Reply