it''s not rails, it''s the webserver in front of it, which
decides whether and
where subdomains get mapped to.
If your ISP handles the webserver at your foo.com domain, then you have to
stick to what you get, if you configure it yourself, then look out for the
doc on how to do it propperly
On 3/30/06, Arch Stanton <d6veteran@gmail.com>
wrote:>
> New to Ruby on Rails. I''ve been playing around with an application
I set
> up at rails.foo.com.
>
> Basically this means that all my pages tied to the application live on
> that subdomain. Is there any reason for not just installing onto your
> parent domain foo.com and putting your static pages in the public dir
> that ruby on rails creates?
>
> The answer seems like a simple yes, however all the install docs I
> looked at indicate a subdomain installation.
>
> Why?
>
> Thanks.
>
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
--
Roberto Saccon - http://rsaccon.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060331/48a0a829/attachment.html