I am in a situation that I have no idea how to approach. Basically,
I've got a licensing app that is distributed across several domains,
as in:
admin.example.com
licenses.example.com
secure.example.com
paypal.example.com
...
Ideally, I would like to be able to setup routing on a subdomain basis
but this is not possible with Rails* (I saw some results on Google
about people trying to do this but none of the solutions were
completely working in a integrated fashion throughout the whole
framework)
I also looked around at other frameworks but I didn't find one which
handled this sort of situations properly. The other option I was
thinking about was using the same model objects in different apps for
each subdomain but I'm not sure whether this is the right way handle
this sort of thing. Any tips on how to approach the problem are
greatly appreciated.
I've got a licensing app that is distributed across several domains,
as in:
admin.example.com
licenses.example.com
secure.example.com
paypal.example.com
Ideally, I would like to be able to setup routing on a subdomain basis
...
thinking about was using the same model objects in different apps for
each subdomain
It's not clear to me what you're trying to achieve -- how would the
response to a request for `secure.example.com/foo` differ from the
request for `paypal.example.com/foo`, for instance?
Or to put it another way, *can* these subdomains operate logically
as uncoupled applications, or are they more `example.com/paypal/`
and `example.com/secure/`?
If you do need them all serviced by one app, fronting it with Apache
httpd with mod_rewrite would probably take care of it.
> I've got a licensing app that is distributed across several domains,
> as in:
> admin.example.com
> licenses.example.com
> secure.example.com
> paypal.example.com
> Ideally, I would like to be able to setup routing on a subdomain basis
...
> thinking about was using the same model objects in different apps for
> each subdomain
It's not clear to me what you're trying to achieve -- how would the
response to a request for `secure.example.com/foo` differ from the
request for `paypal.example.com/foo`, for instance?
Their URLs would form an empty intersection but secure.example.com
would map '' to the StoreController while admin.example.com would map
'' to the AdminController.
Or to put it another way, *can* these subdomains operate logically
as uncoupled applications, or are they more `example.com/paypal/`
and `example.com/secure/`?
They can work as example.com/secure/ and example.com/paypal/ etc. I'm
not sure if that matters but secure.example.com would have to go
through SSL.
If you do need them all serviced by one app, fronting it with Apache
httpd with mod_rewrite would probably take care of it.
That brings up the question on how to handle URL generation, since a
URL for the admin controller would have to generate admin.example.com
instead of example.com/admin.
If you do need them all serviced by one app, fronting it with Apache
httpd with mod_rewrite would probably take care of it.
I'd still consider whether multiple loosely coupled apps would be
suitable, even desirable -- but in any case...
That brings up the question on how to handle URL generation, since a
URL for the admin controller would have to generate admin.example.com
instead of example.com/admin.
True. Again, if you're willing to stick with Apache httpd, mod_filter or
mod_substitute might be appropriate (rewrite the outbound URLs ).
But generating them directly would obviously be preferable. Time to
go experiment a bit
