Red Hat
Sep 24, 2012
by The Entire TorqueBox Team

We're as happy as a moth in a sweater factory to announce the immediate availability of TorqueBox 2.1.2! This is a bug-fix only release and is a recommended upgrade for anyone running TorqueBox 2.1.0 or 2.1.1.

Highlights of major changes

  • We have a new Getting Started Guide that walks Windows, RVM, and Mac / Linux users through downloading and installing TorqueBox, deploying simple Rails and Rack applications, and adding basic TorqueBox features to an existing application.

  • We fixed a bug in our handling of cookie headers caused by a misinterpretation of the Rack spec. If you had a Rails application that was setting cookies explicitly in addition to using session cookies and had unexplained issues with cookies going away, this is the reason and it's now fixed.

  • Some users with Rails applications were seeing a large number of already initialized constant warnings during TorqueBox boot - these should no longer appear.

  • We're a bit smarter about finding Bundler when torquebox run is used within an application that uses bundle install --deployment. If you've been fighting with errors like no such file to load -- bundler/setup this should fix them.

  • We're much looser in our Thor dependency requirement for the torquebox gem so any error caused by TorqueBox requiring a Thor version that was incompatible with other gems should be fixed.

  • The parsing of database.yml to setup XA datasources has been improved to handle basic ERB usage, like reading environment variables. If you previously had to add xa: false to your database.yml and it contains ERB, try removing xa: false and see if things work.

Upgrading from 2.1.1

Our goal with 2.1.2 was to be backwards-compatible with 2.1.1, so there shouldn't be any special steps needed for the upgrade. None of the underlying AS7 xml configuration files or torquebox.yml / torquebox.rb files need any changes.

Roadmap update

This is the last anticipated release in our 2.1.x line. The next release is 2.2.0, currently scheduled for October 29th. The feature list of 2.2.0 is probably a bit too aggressive so don't be surprised if some things get bumped to 2.3.0. Head on over to the roadmap page and make sure you vote for any features you'd really like in 2.2.0 so we can prioritize accordingly.

Don't be a stranger!

As always, if you have any questions about or issues with TorqueBox, please get in touch.

Issues resolved since 2.1.1

  • [TORQUE-802] - Explain concurrency setting better.
  • [TORQUE-805] - Favicon for BackStage
  • [TORQUE-841] - torquebox-capistrano-support always sets ruby version to 1.8 in the external descriptor which will prevent settings in the internal descriptor
  • [TORQUE-859] - Lots of constant already initialized warnings when booting Rails apps
  • [TORQUE-913] - `torquebox rails` does not properly detect if a directory already contains a Rails app
  • [TORQUE-917] - Backstage logs Invalid or misspelled option: credentials
  • [TORQUE-920] - When deployed with HTTP auth, Backstage ignores "production" env flag, defaulting to "development"
  • [TORQUE-922] - Web pool defaults to lazy if web pooling config given but lazy not specified
  • [TORQUE-925] - Create Getting Started Guide
  • [TORQUE-927] - Torquebox upstart should default to max 4096 open files
  • [TORQUE-930] - database.yml with ERB causes invalid XA error when creating jdbc datasource
  • [TORQUE-931] - Torquebox declares strict dependency on thor (0.14.6) which prevents installation with padrino (which requires ~> 0.15.2)
  • [TORQUE-932] - Messages w/ marshal encoding cannot be decoded more than once
  • [TORQUE-937] - Rack cookie headers are not processed as expected through Torquebox
  • [TORQUE-940] - Binary distribution doesn't include .bat stubs for bundle and torquebox commands
  • [TORQUE-944] - TorqueBox can't find bundler/setup when app uses bundle install --deployment

Image © Copyright Mark A. Wilson and licensed for reuse under this Creative Commons License. The original can be be found here.

Original Post