On 6 Nov 2012, at 12:01 PM, "J.W. Bizzaro" <[email protected]> wrote: > I'm helping Maurice with this. We're running Apache on Linux with mod_wsgi. > This is a shared host environment where each hosted website is under the > user's public_html directory. Normally, we run symlinks from the docroot to > the hosted website as follows: > > ln -s /path/to/username/public_html/websitename /path/to/httpdocs/websitename > > And the URL becomes http://www.bioinformatics.org/websitename > > In this case, "websitename" is "refgene". > >> 1. http://www.bioinformatics.org/refgene gives me an Invalid request > > What's the whole message? There should be some details. > > That's it. Is there a way to make it more verbose? > > You want web2py in a directory called web2py. If you write an app called > refgene, it will live in web2py/applications/refgene. > > Does it matter if the URL contains the name web2py or not? We can name the > directory itself anything internally, as long as the URL > isn'thttp://www.bioinformatics.org/web2py. An important part of the hosting > is to give a website (refgene) its own URL.
The directory name really doesn't matter, so I suppose refgene is as good as any. But the name of the directory is irrelevant to the URL. Your wsgi configuration should be pointing to wsgihandler.py in the web2py root directory, wherever that happens to be. I'm not much of an expert there, but I can help with routing once you have web2py up and running *without* routing. Remove any routes.py until you've got things working. --
