Well, I guess I’m successful because within a month of getting my very
first
application online (and it’s barely functional) I now have to get a
second
one up pretty quickly.
Basically, I have a rails application “myFirstApp”, and a hostname www.myfirstapp.com. Now I have a second rails app “mySecondRailsApp”
and I
need www.mysecondapp.com to peacefully coexist on the same box.
I’ve looked through the rails wiki and I know I need virtual hosting. I
see
one page that discusses this with apache and I might be able to muddle
through it. Currently I’m using WEBrick and I’m a big fan of not
changing
things unless I have to. Can this be done well with WEBrick or should I
make the switch to ?Apache?
Server load is not an issue. Both sites are low traffic.
Still working on my first app on a test server, but it needs to go onto
a
production system as well. I use vhosts on the production environment,
having
it all directed by apache2.
What I’m planning on doing (read: trying/testing). Is have an apache
daemon
function as a proxy and redirect stuff to a lightweight daemon
internally to
another port for the rails apps.