Haecceity

Yup, the long wait is finally over and thanks to a cast of thousands 2.2.3 is now in experimental.

I’d like to extend thanks to Mark and Canonical for sponsoring much of the original work, and also the sprint at the start of this year that got most of the remaining work done.

What we really need now is lots of upgrade reports so we can figure out how much automated help a 2.0->2.2 upgrade can reliably provide, and also where. I’ve been running these packages in production for some time so I’m not that concerned about overall stability, but I’ve not been using some of the weirder modules. We also need to get third-party module packages to stage updated packages into experimental built against 2.2

Quick entry on how this blog is coming to you, should anyone happen to care.
It’s a Typo install off Typo’s Subversion trunk. This pulls in trunk of Rails via an svn:external.
Originally I was going to be super-brave and use the FCGI proxy module backported from Apache trunk, but I decided I’m not that brave, so I used some slightly less bleeding edge code.
I upgraded to Apache 2.2.2 and ensured I had mod_proxy_balancer , mod_proxy_http and mod_proxy loaded.
I then installed Mongrel and ran that in my typo checkout like so: mongrel_rails start -d -e production -p 3000; this brings up mongrel on port 3000 and sets Rails into production mode rather than the standard development mode.
Having checked that the install on the high port was working correctly, I then configured Apache to properly connect to it. First I set up a very small - I only have one server, but I wanted to play with the technology - balancer config:
<Proxy balancer://server>
BalancerMember http://server:3000
</Proxy>
I then set up a VirtualHost as usual, but added the following lines to force content onto the load balancer.
ProxyPass / balancer://server/
ProxyPassReverse / balancer://server/