sherdim, Thank you so much for your reply !!!!

To be honest, I cannot really understand routes even I read the book.
I don't even know if I should copy the applications under web2py
folder and/or where to ...

Here's my directories:
-----------------------------------------------
python:
C:\Python25

web2py:
C:\Python25\web2py

web2py appllications:
C:\Python25\web2py\applications

Created by 2.3. Configure WSGI handler:
C:\w2p\applications (Empty)
is link to...
C:\Python25\Lib\site-packages\applications (Empty)

I start web2py like this:
c:\Python25\web2py>python web2py.py

Virtual Directory on IIS
"ochibaapp" (renamed from "appname") under "Default Web Site"
-----------------------------------------------



On Sep 9, 9:09 am, sherdim <sher...@gmail.com> wrote:
> Hello Omi!
>
> first, junction (as you read in receipt) is needed for ability to launch
> development version of web2py on the same source.
> anyway you can copy all web2py folder and syncronize them as needed
>
> Step 2.3.2 Configure routes - is standard for web2py and described in the
> book.
> it sets relative path to your application files.
>
> In the beginning you should realise where are your application directories.
> You should check they are workable with standard web2py.py launcher.
>
> Then check permissions for folders - so IIS can access them with given
> credentials (it is described in the receipt).
>
> you should skip 2.3.4 - it has sense on big production server if any
>
> As I see your isapi_web2py.py script cannot access application files
> (directory is empty)
> try at first simple copy instead junction
>
> In the end of 2.3.1 there are typos in path - slashes are escaped - be
> careful or just allow "All Unknown ISAPI Extentions".
>
> for testing try in the section for interactive launch of isapi_web2py.py
> script
>
> if __name__=='__main__':
>   import gluon.main
> call from command line - to be sure gluon is on the path and accessible
>
> Write here your directory configuration if you are still lost.
> Think about web2py directory as a single ready application which just should 
> plugged to IIS.
>
> Best regards

Reply via email to