If you plan to run the *same* web application for different
entities - thus you need different data (icons, templates,
db...) in your app - maybe it's better to check for
environ['HOST'] in your controllers explicitly, and act acordingly?
- The subdomain chooses the controller which
If you plan to run the *same* web application for different entities -
thus you need different data (icons, templates, db...) in your app -
maybe it's better to check for environ['HOST'] in your controllers
explicitly, and act acordingly?
After a while, I'm sure a pattern will emerge so you
On Nov 12, 5:11 am, Andrew Smart [EMAIL PROTECTED] wrote:
My use case shouldn't be uncommon. Having an static HTML website which can't
be changed (e.g. intranet server), and having an external pylons app
serving under a subdomain.
(cough, splutter) - I had planned to do this on my new site.
Andrew Smart wrote:
Hi folks,
I have the following setup:
- one webserver serving the public avaiable domain (www.thisdomain.com)
- a subdomain is pointing to a app server (shop.thisdomain.com) running on a
different server
My routing:
shop_conditions = dict(sub_domain=[shop,])
Von: pylons-discuss@googlegroups.com
[mailto:[EMAIL PROTECTED] Im Auftrag von Ian Bicking
Gesendet: Montag, 12. November 2007 19:28
An: pylons-discuss@googlegroups.com
Betreff: Re: Routes: Subdomain won't work with referers (bug?)
Andrew Smart wrote:
Hi folks,
I have
-Ursprüngliche Nachricht-
Von: pylons-discuss@googlegroups.com
[mailto:[EMAIL PROTECTED] Im Auftrag von zunzun
Gesendet: Montag, 12. November 2007 19:25
An: pylons-discuss
Betreff: Re: Routes: Subdomain won't work with referers (bug?)
On Nov 12, 5:11 am, Andrew Smart [EMAIL
_
You also turned on the sub_domains option on the mapper?
Yes, I did.
http://wiki.pylonshq.com/display/routes/Manual#sub-domain-support
BTW, I'm not entirely sure why you need to use the sub-domain option at all.
The sub_domain option is so that a Pylons app can decide to respond
