how should I implement dynamic subdomains?
Yanni Chiu
yanni-bJEeYj9oJeDQT0dZR+AlfA at public.gmane.org
Sun Jul 11 05:27:38 UTC 2010
Jamon Camisso wrote:
> That seems terribly inefficient, forking or restarting incurs a large
> performance penalty.
Each app server would be started on demand, and self-terminate when
inactive. At this point, making my app server support multiple sites
seems harder than kicking off instances for each site.
> Using the application you're deploying to handle new subdomains instead
> of reloading Apache would be easier. For example, Drupal, Wordpress etc.
> have multi-site support that runs off a single codebase.
Okay, I'll look into how they support multi-site.
> That way you can have a static Apache VirtualHost for *.foo.com and let
> your application handle the logic or serving up particular subdomains.
> It also keeps things limited to ports 80 and 443 as Ted Leslie pointed out.
--
The Toronto Linux Users Group. Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
More information about the Legacy
mailing list