* Passenger supports using various gemsets very easily using the setup_load_paths.rb file in the config of your app (though multiple ruby versions still seem to be a problem).
* If you're using passenger, why do you have each app running on a different port? Using the Passenger Prefs Pane makes it trivially easy to have each app at its own appname.local URL (though, admittedly, installing an extra prefs pane, where Pow has it built in, gives bonus points to the latter).
* Same with my last point. Passenger automatically handles the booting up or apps when you access their URL in the browser, just like Pow does. Of course, I'm guessing you don't have Passenger installed this way if each app has to run on a different port.
* Passenger supports using various gemsets very easily using the setup_load_paths.rb file in the config of your app (though multiple ruby versions still seem to be a problem).
* If you're using passenger, why do you have each app running on a different port? Using the Passenger Prefs Pane makes it trivially easy to have each app at its own appname.local URL (though, admittedly, installing an extra prefs pane, where Pow has it built in, gives bonus points to the latter).
* Same with my last point. Passenger automatically handles the booting up or apps when you access their URL in the browser, just like Pow does. Of course, I'm guessing you don't have Passenger installed this way if each app has to run on a different port.