it's not rails, it's the webserver in front of it, which decides whether and where subdomains get mapped to.<br>If your ISP handles the webserver at your <a href="http://foo.com">foo.com</a> 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
<br><br><div><span class="gmail_quote">On 3/30/06, <b class="gmail_sendername">Arch Stanton</b> <<a href="mailto:d6veteran@gmail.com">d6veteran@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
New to Ruby on Rails. I've been playing around with an application I set<br>up at <a href="http://rails.foo.com">rails.foo.com</a>.<br><br>Basically this means that all my pages tied to the application live on<br>that subdomain. Is there any reason for not just installing onto your
<br>parent domain <a href="http://foo.com">foo.com</a> and putting your static pages in the public dir<br>that ruby on rails creates?<br><br>The answer seems like a simple yes, however all the install docs I<br>looked at indicate a subdomain installation.
<br><br>Why?<br><br>Thanks.<br><br>--<br>Posted via <a href="http://www.ruby-forum.com/">http://www.ruby-forum.com/</a>.<br>_______________________________________________<br>Rails mailing list<br><a href="mailto:Rails@lists.rubyonrails.org">
Rails@lists.rubyonrails.org</a><br><a href="http://lists.rubyonrails.org/mailman/listinfo/rails">http://lists.rubyonrails.org/mailman/listinfo/rails</a><br></blockquote></div><br><br clear="all"><br>-- <br>Roberto Saccon -
<a href="http://rsaccon.com">http://rsaccon.com</a>