> Going back to my original question - can anyone provide a domain specific > Apache virtual host file that achieves what Massimo's routes.pu settings do > and does not require a separate instance of web2py for each domain. (I'm > not sure how to achieve this from what VP posted.)
I am also interested in learning a configuration that allows this. Someone please help! On Oct 20, 4:05 am, Tom Atkins <[email protected]> wrote: > That makes sense about routes.py for multiple sites not being a production > setting because web2py will be serving static files. Also, this is the same > for the "Tip of the day. The power of routes" setup (perfect for me now with > small development sites but hopefully not in the future)! > > Going back to my original question - can anyone provide a domain specific > Apache virtual host file that achieves what Massimo's routes.pu settings do > and does not require a separate instance of web2py for each domain. (I'm > not sure how to achieve this from what VP posted.) > > Thanks! > > On 19 October 2010 03:40, mdipierro <[email protected]> wrote: > > > The Apache options is better because allows you to also map static > > files. > > In my examples web2py was serving static files and that is not a > > production setting. > > The apache routes config is more portable (does not depend on web > > server). > > > Massimo > > > On Oct 18, 9:07 pm, VP <[email protected]> wrote: > > > The way I did this is through Apache, by adding > > > > ServerName domain.com > > > ServerAlias *.domain.com > > > > to the web2py configuration section in site-enabled/000-default > > > > Which one is more preferable? pros and cons? > > > > Thanks. > >
