Updated NGINX Passenger packages will follow shortly (they’ll be available via a separate ppa)

Updated NGINX Passenger packages will follow shortly (they’ll be available via a separate ppa)

We’ve also fixed the dependency problems that occurred in the past, where a newer version of Passenger broke the older NGINX packages. These NGINX packages now strictly depend on the Passenger packages, and we’ve put them in their own Launchpad archive so they’re always guaranteed to work (even if they ever lag behind the Apache packages).

You can add the PPA and install NGINX like this:

sudo apt-add-repository ppa:brightbox/passenger-nginx
sudo apt-get update
sudo apt-get install nginx-full

You’ll then need to enable the Passenger module, which can be usually done like this:

cat <<EOF > /etc/nginx/conf.d/passenger.conf
passenger_root /usr/lib/phusion-passenger;
EOF

We’ve also added our other Apache Passenger packages to Launchpad too (with Hardy support), just use:

sudo apt-add-repository ppa:brightbox/passenger

We’ll keep our own apt repository in sync with Launchpad for Hardy and Lucid too, in case you prefer that (use the passenger-nginx component for the nginx passenger packages).

Happy Passengering! (I’m pretty certain that’s not a real verb. It might be a proper verb. I’m pretty certain there is no such thing as a proper verb).

We’ve now got Ubuntu Hardy and Lucid packages available on our apt repository and we consider it ready for production use. Brightbox customers can upgrade from Passengr 2.x simply by running these commands on their Brightboxes:

sudo apt-get update
sudo apt-get install -qy libapache2-mod-passenger

If you’ve not got a Brightbox, you’ll need to add our apt repository key and config first. You can read more about it on our wiki.

We now have Passenger 3.0.0-pre3 packages available for Ubuntu 10.04 (Lucid) and Ubuntu 8.04 (Hardy). As they’re pre-release versions, we don’t recommend them in production just yet and have put them in their own repository to prevent any accidental upgrades.

If you’re not already a Brightbox customer, then you’ll need to set up base access to our apt repository first.

Otherwise, just add the new passenger-testing repository (switch “lucid” to “hardy” if you’re on Hardy):

sudo sh -c 'echo "deb http://apt.brightbox.net lucid passenger-testing" > /etc/apt/sources.list.d/brightbox-passenger-testing.list'

Then you can upgrade/install 3.0.0-1bbox1~pre3

apt-get update
apt-get install libapache2-mod-passenger

Passenger now has a native library, which depends on your version of ruby. For simplicity, these packages currently require the ruby1.8 packages to be installed. You can, of course, switch to ruby1.9 and passenger will auto-compile the necessary native support for you. We’ll be providing packages for 1.9 support soon, so you won’t need to rely on the auto-compiling.

For further information on using these packages see the release announcement for our Ruby EE 2010.01 packages.

As with our other Ruby EE packages, they upgrade (i.e replace) the standard 1.8 Ruby installation. This means all your gems stay the same, and everything on your system immediately starts using them (Phusion’s own Ubuntu packages do not work like this).

These packages are also the best way to get Ruby 1.8.7 on Hardy, which you’ll need if you’re playing with Rails 3.

If you’re on a Hardy based Brightbox, just create or edit /etc/apt/sources.list.d/brightbox-rubyee.list to contain the rubyee-testing component like so:

deb http://apt.brightbox.net/ hardy rubyee-testing

If you’re on one of our Lucid beta boxes provisioned before today, simply create /etc/apt/sources.list.d/brightbox-rubyee.list and add the rubyee component:

deb http://apt.brightbox.net/ lucid rubyee

Finally, update and upgrade libruby1.8:

sudo apt-get update
sudo apt-get install libruby1.8 irb1.8 libopenssl-ruby1.8 libreadline-ruby1.8 rdoc1.8 ruby1.8

If you’re not on a Brightbox, see the instructions on our wiki first. The wiki also documents how to revert back to the old packages.

We’ve built our Ubuntu Hardy packages for i386 and AMD64 architectures which are now available from the Brightbox apt repository.  We’ve also upgraded our librack-ruby packages to 1.1.0.

This package won’t actually support Rails 3 just yet though as we’ve yet to package and test the librack 1.1.0, which Rails 3 depends on.  We’re working on it now and once we’re happy with it we’ll add new packages to our repository as usual.

As usual, details on installing the packages from our repository are available on our wiki.

If you’re using Passenger and it’s making you happy, please do consider supporting its development by donating money in the form of an “Enterprise License” direct from Phusion, the company behind it.

As with our other Ruby EE packages, they upgrade (i.e replace) the standard 1.8 Ruby installation. This means all your gems stay the same, and everything on your system immediately starts using them (Phusion’s own Ubuntu packages do not work like this).  We’ve tested it with the usual Railsy native gems, RMagick, Mongrel, fasthread etc. and have had no problems.

If you’re on a Brightbox, just edit /etc/apt/sources.list.d/brightbox-rubyee.list and change the rubyee component to rubyee-testing:

deb http://apt.brightbox.net/ hardy rubyee-testing

Then update and upgrade:

sudo apt-get update
sudo apt-get install libruby1.8

If you’re not on a Brightbox, see the instructions on our wiki first. The wiki also documents how to revert back to the old packages.

As said above, we now have 64bit packages available too (which was recently made easier by some Debian package dependency updates, also included in our repository).

Please let us know how they worked out for you on our forum. Thanks!

Passenger 2.2.4 actually is just a small bug fix release for a memory leak in 2.2.3, but obviously brings all the benefits of 2.2.3 too.  A huge number of bugs have been fixed, particularly the “Broken Pipe” errors some sites under heavy loads were experiencing.

As usual, details on installing the packages from our repository are available on our wiki.

If you’re using Passenger and it’s making you happy, please do consider supporting its development by donating money in the form of an “Enterprise License” direct from Phusion, the company behind it.

This new version of Passenger brings a train-load of NGINX fixes, so our Passenger enabled nginx-brightbox package has been updated too and is available in our testing repository.  More details on using our testing repository here in the 2.2.1 announcement blog post.

We’ve had to restructure the way our Ubuntu packages are built to enable installation of the NGINX extension, so needs more extensive testing than usual.  The packages are now available for Ubuntu Hardy in our testing repository.

You’ll need to add our testing repository to your apt sources list. And if you’re not on a Brightbox, you’ll need to import our key and add our stable repository too.

Once you’ve done that, you can install the new version of Passenger.  If you’re wanting to just install the Apache version:

sudo apt-get update
sudo apt-get install libapache2-mod-passenger

This will pull in a new dependency, passenger-common.

If you just want to get stuck in with the new NGINX support, install the nginx-brightbox package:

sudo apt-get update
sudo apt-get install nginx-brightbox

This will also pull in the passenger-common dependency. This is NGINX 0.6.36 plus some useful modules: upload progress, upstream fair, geoip, ey-balancer and access key. It will replace any other NGINX packages you have installed (NGINX does not support dynamic modules like Apache).

You can install both Apache and NGINX side by side, but you’ll obviously need to run them on different ports.

The 2.2.1 Apache package has already had quite a bit of testing by us, but the NGINX package has had very little. We’ve already come across a Passenger bug with reloading NGINX (reported here), though we expect this will be fixed quickly.  So basically, these are good to play with but not for production just yet.

If you need any help with these packages, try our Passenger support forum.

The details are on the usual page on our wiki.  If you have any problems or need any help, try our forums.

The new packages depend on new versions of the Ruby rack libraries (not the gem), but this is provided in our repository too and will be automatically installed. You need to install the fastthread gem yourself though.  Our repository provides a few other useful Hardy packages too.

We are only testing our packages against Ubuntu Hardy right now, but they should install and run fine on newer versions of Ubuntu too.

Remember, for maximum memory savings (and speed improvements) try our Ruby Enterprise Edition packages for Ubuntu Hardy (currently only 32bit packages available).

Every Brightbox runs Ubuntu, which is an operating system built on top of the GPL Linux kernel. Our infrastructure is built upon Xen, Apache, Nginx, MySQL, Nagios and many other open source software projects; not least of which are Ruby and Rails themselves.

But whilst we benefit from this software, without contribution, free software is nothing, so we contribute anything we can. The most obvious of these are the Brightbox deployment gem and its associated server-side tools. These are extensions to Capistrano that help you get your application onto your Brightbox as quickly and easily as possible.

We also have our apt repository where we repackage a number of free software projects to make configuring your Brightbox as easy as possible. More details on the repository are available on the wiki, but the most notable are our Passenger and Ruby Enterprise Edition packages.

However, nowadays, the real place for sharing your code is on Github. We have a number of projects available there, ranging from the tiny to the large.

These include:

• Flashing rails

  A rails plugin that makes it simple to display flash messages in your views in a consistent manner.

• Rujitsu

  A simple gem that collects together a number of convenience methods and various helpers.

• RSpec-rails extensions

  A gem that tidies up specifying your code with RSpec-Rails.

• Object Factory

  Brightbox’s very own answer to Factory Girl or Machinist that lets you build your test data with minimal configuration and no fixtures.

• Altered Beast and Redmine.

  We have taken our own forks of two popular Rails applications. David’s version of Altered Beast handles the Brightbox forums and Redmine handles our internal bug tracking and task lists.

• Warren and Bigwig

  Last, but by no means least, we have Warren and Bigwig. These are our wrappers to AMQP and RabbitMQ.

  We use RabbitMQ internally to deliver messages across our various infrastructure systems and needed a simple way to interface our ruby code to Rabbit (which is implemented in Erlang).

  This led to Warren, our wrapper over the AMQP protocol that make it simple to post messages onto the queue.

  In order to receive and act on those messages, we also built Bigwig (no prizes for spotting the rabbit references there), which takes those messages and responds. Bigwig matches each incoming message against a set of plugins, each plugin being small and focused on a particular task. Unrecognised messages are discarded, ensuring that rogue commands can’t wreak havoc upon our network.
  UPDATE: It turns out that Bigwig isn’t quite ready yet, as a big chunk has been rewritten. We’ll get it out there as soon as we can.

As these are all free software projects, please take a look inside and poke around. Any suggestions, improvements, patches or forks will be gratefully received. Also, stay tuned for an announcement on a major project we are looking to start in the next couple of weeks.

Update 2: We’ve also put the code for Isitruby19.com onto Github, under an MIT licence. Please go to the forum if you have any questions.

We’ve made it super easy to deploy your application using Passenger instead of the mongrel configuration recommended previously and there is documentation on how to use this on your Brightbox over at our wiki. New deployments are ready to go on Passenger immediately provided you have Ubuntu Hardy 8.04 already installed on your Brightbox. If you’re still on Ubuntu Dapper 6.06 then you can upgrade by simply ordering a new box, moving your data over and then cancelling the old box.

There is no automated way to move existing mongrel installs over to Passenger, but there is a very simple procedure outlined on the wiki page which will have you up and running in a few minutes.

If you have any questions or spot any bugs in this latest release then please let us know, we now have a forum on which we will be happy to answer your Passenger and Brightbox gem questions.

Update 12/01/2009: After spotting a regression which snuck in just before we released version 2.2, version 2.2.1 has just been released and should be propogating around the Rubyforge mirrors right now.

Update 2 13/01/2009: I found a better way to handle passenger restarts. This has been added to the gem and the version has been bumped to 2.2.2

We’re now also providing 64bit versions of the packages (the source of the 404 errors some of you reported when trying to install the package).

Documentation for the packages in the usual place on the wiki.

More Passenger news coming soon :)

The quick answer is (stop press) within the next few weeks. Read on for the longer version :)

There are a couple of things we need to do before “officially” supporting Passenger on Brightbox…

1. We need to complete the packaging of Ruby Enterprise Edition for Ubuntu Hardy (which John is working on right now)
2. We need to update the Brightbox gem to support deployment and management with Passenger – as well as Apache/Mongrel and Nginx/Mongrel (which it will continue to do).

Neither of these are particulary mammoth tasks, but we do have a lot of internal projects going on at the same time such as improving the control panel (watch this space) as well as the day-to-day work of running a hosting company and managing clusters for some very large customers [plug].

Stay tuned over the next few weeks as we announce Passenger support together with a very special discount offer!

Why not join our announcements list to stay up to date?

Particularly of note, this fixes a deadlock bug using Passenger and global queueing with the Apache worker mpm.

As before, documentation for our packages is available on our Passenger wiki page.

As before, documentation for our packages is available on our Passenger wiki page.

The previous version was faulty and resulted in mod_passenger.so being installed in the root dir (doh!) – I’m not sure when that bug crept in.

I’ve also updated the dependencies slightly – it will no longer require the rubygems package.  This helps those of you who have installed gems manually and would rather not use the Ubuntu packages.  If you didn’t install gems manually, you’ll need to explicitly specify the package now.

This, and a little more information can be found on our Passenger wiki page.

If you need help using these packages, or would like to feed back your experiences, go on over to the discussion forum.

Accepted into Ubuntu Intrepid Ibex

And if you weren’t aware, our package was accepted into the official Ubuntu repository (in the universe component) so if you’re using Ubuntu Intrepid Ibex, you can use it straight away! (though it does require the packages rubygems).  Another step towards Ubuntu being the perfect rails stack. The source package page can be found here.

Next up, Ruby Enterprise Edition packages…

• Merb Support via Rack
• Lower VM Usage
• Better load balancing and non-blocking file uploads

The package is on our repository at http://apt.brightbox.net and built for Ubuntu 8.04 (Hardy).

I’ve had the pleasure of working with Hongli at Phusion to knock out a few bugs and make Phusion Passenger easier to package. That work has paid off and I was able to quickly release the updated Passenger package within minutes of getting the nod from the Phusion guys.

That’s why we love Free Software here at Brightbox.