Thanks alot for sending me down the right path Ashley.
I looked up ProxyPass and ProxyPassReverse, do I need both?
Yes, or things like redirect will fail - because Apache needs to rewrite response headers that come out of the rails server that will contain localhost instead of the real hostname of the server. The host config will look something like
Allow from all
# or possibly <Location /my_app>
Also, should I simply point Apache to the /work/demo directories that I
created with the ruby script?
No need unless you want apache to server static content directly. I've never bothered with that because I've never managed anything where it's become an issue. I don't think it's hard to do though. When you are using proxying, the rails app can be on a different physical server - indeed that's the principle behind horizontal scaling, which is achieved in apache using mod_proxy_balancer. But for simple cases you don't need to worry about that. (At work, we've got two apache servers that are load-balanced. Our rails apps run in mongrel on the same servers, and each apache proxies to its own local mongrels only, so our apache configs would be the same as yours despite the extra redundancy)