SwitchPipe Development Effectively Stops

[Peter Cooper]

SwitchPipe was started as a stopgap solution for easily deploying Ruby
Web applications.

Phusion Passenger 2.0, released today, now deals with Rack, so
theoretically any Ruby app can be tailored to work with it, resolving
the deployment issue. http://www.railsjedi.com/posts/52-The-Holy-Grail-for-Rails-Deployment

I will continue to use SwitchPipe until it ceases to be of use for me,
as well as continue to fix bugs, but in terms of new development,
SwitchPipe has been superseded and rendered obsolete for Ruby use.

Thank you for your support!

[Kamil Kukura]

I was using Switchpipe and then started to use Phusion Passenger. Now
I'm thinking to switch back because of resources consumed by
passenger. When running only one instance of Typo blog (http://
www.csonrails.net) the processes look like:

Rails: /var/www/vhosts/csonrails.net
Passenger FrameworkSpawner: /var/www/vhosts/csonrails.net/vendor/rails
Passenger FrameworkSpawner: 2.1.0
/opt/ruby-enterprise/lib/ruby/gems/1.8/gems/passenger-1.9.1/ext/
apache2/ApplicationPoolServerExecutable...
Passenger spawn server

That's too much for my VPS. Switchpipe is much better at this. What I
would like to see is some "control panel" where one could restart
applications, see statuses and so on. Some ideas how to implement it?