3 ms·
In principle I agree with what you're saying but Torquebox has been something I've had to constantly work on whereas Passenger has always been, more or less, de
by PetrolMan 14y ago
In principle I agree with what you're saying but Torquebox has been something I've had to constantly work on whereas Passenger has always been, more or less, deploy and forget.
I've been using Torquebox since version 2.0.1 (not that long really) but I've never really had a completely stable server. Deployment has always been somewhat of a hassle and recently the HA cache has been so broken that I have not been able to use torquebox in a cluster.
In the end, I'm just happy to have another option. The more the merrier.
- bradleyland 14y agoInteresting, but not all that surprising. People are often perplexed by the fact that we continue to stick with Passenger, as opposed to jumping on the bandwagon with the latest and greatest. Passenger is the one piece of my infrastructure that I never have to touch. It also comes with a great toolchain for instrumenting (status and memory usage tools). I've been tempted by TorqueBox in the past, but never made the jump to actually build an app with it.