Ruby on Rails Wednesday, November 24, 2010

Hi Peter, thank you for the reply

> Much in the same way you handle subdomains, but with the complete
> domain as a value in your database instead of just the subdomain.

mmm..ok, i'll try it out, considering that i'll have to manage both
domains and external domains

> This is more complicated. You need to do it in a similar way as
> omniAuth does for Twitter/Facebook/OpenID/ logins.

could you please explain better this part? or if you have some
docs/posts i can read about

> You should automate it then. You will basically write to the Apache
> vhost conf files (and possibly the dns server configs) and reload the
> configuration from your Rails app. The main concern here should be
> handling the security on the system level. As long as the user then
> goes to the full domain, all links will stay within that domain.

what about an approach like set a dedicated ip for the app, and in the
apache config accept all the requests to that ip and be managed by the
rails app. In that way the user could simply change the A record of his
domain and it should kinda work (i've not tried it yet, but iirc in the
apache config is possible to do something like this... i don't know with
nginx though)

Thanks

--
Posted via http://www.ruby-forum.com/.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

No comments:

Post a Comment