Does each revision have its own set of static files which also need to
be mapped explicitly by Apache in order to be served up?
Graham
--
You received this message because you are subscribed to the Google Groups "modwsgi" group.
To post to this group, send email to mod...@googlegroups.com.
To unsubscribe from this group, send email to modwsgi+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
Have a read of the thread:
http://groups.google.com/group/modwsgi/browse_frm/thread/d0b1d5eb77f56d77
There are various suggestions in there of how to do the sort of thing
you want, including trying to provide a way to allow instances for a
specific revision to be delegated to their own daemon process group to
keep them distinct from others.
Especially see the VirtualDocumentRoot examples. Indicate whether you
have any restrictions on being able to use VirtualDocumentRoot and
then we can go from there or refine that method.
Graham
On Jun 16, 5:18 am, Ian Bicking <i...@colorstudy.com> wrote:
> It's a little involved (well, a lot involved), but Silver Lining does this:http://bitbucket.org/ianb/silverlining/src/tip/silverlining/server-ro...
>> case I use one wsgi file (http://bitbucket.org/ianb/silverlining/src/tip/silverlining/mgr-scrip...)
> Basically you need a WSGIApplicationGroup for each environment, and in my
> that uses environ['HTTP_HOST'] to find and activate the environment.i did look at toppcloud when it started but if i understood correctly
it was focused on rackspacecloud and i'm targeting amazon services.
also, i'm using fabric to manage python2.6 on ubuntu karmic and lucid
(official releases for aws ec2) with postgres 8.4, apache/mod_wsgi and
rabbitmq.
does silverlining target specific releases based on linux distro
available at rackspacecloud or something else?
i'll take a look at your workflow, i'm sure i'll find something
useful.
i didn't have time to properly read docs and test configurations (hope
i'll have time next week) but i have some questions and would
appreciate any comments.
silverlining approach to use a single wsgi file to handle app
revisions is interesting and i was wondering if anybody would like to
comment pros/cons on using apache config vs. wsgi file to handle app
revisions?
i've been playing with VirtualDocumentRoot and it looks ok but i can't
find what is the problem when used instead of VirtualHost?
i did get an impression that for some reason i shouldn't mix
VirtualHost and VirtualDocumentRoot although i'm not sure why (am i
just wrong here?).
if i use VirtualDocumentRoot as default config can individual domains
(or subdomains) be configured separately?
Aljosa
I think (cant remember for sure), if you are using VirtualDocumentRoot
at global scope in Apache configuration you cant use VirtualHost at
the same time.
If however you need to use VirtualHost, you can still use
VirtualDocumentRoot inside of the VirtualHost to map to varying
document root where you have a ServerAlias that matches multiple names
for that VirtualHost.
Graham