Onmi, it is not clear - whether you have separate domain for the site under
IIS. if no - then you can use default pathes.
To be honest, I cannot really understand routes even I read the book.
>
routes.py is not related to deployment on IIS. You can skip routes
configuration upto you need/want it.
for beginners I would suppose such if your app called "ochibaapp", not
"welcome":
========
routers = dict(
BASE = dict(default_application='ochibaapp',
domains={ 'ochiba.com' : 'ochibaapp' },
root_static = ['favicon.ico', 'robots.txt', 'sitemap.xml'],
),
)
======
Here's my directories:
> -----------------------------------------------
> web2py:
> C:\Python25\web2py
>
I am not sure - will python include gluon from this dir automatically?
More advantageous place - \Python25\Lib\site-packages\gluon
So my proposal - copy gluon dir to C:\Python25\Lib\site-packages\
> web2py appllications:
> C:\Python25\web2py\applications
>
so C:\w2p\ in the slice become C:\Python25\web2py in your current placement
> Created by 2.3. Configure WSGI handler:
> C:\w2p\applications (Empty)
> is link to...
> C:\Python25\Lib\site-packages\applications (Empty)
>
> reverse order!!! link (junction) the second one to
C:\Python25\web2py\applications
> I start web2py like this:
> c:\Python25\web2py>python web2py.py
>
this can be used for development and debugging
> Virtual Directory on IIS
> "ochibaapp" (renamed from "appname") under "Default Web Site"
>
this app must point to C:\Python25\Lib\site-packages\_ochibaapp.dll
or whatever name you used (through wildcard mapping in the app config)
(According to name agreement - DLL must be named _filename.dll for
filename.py )
So in the file C:\Python25\Lib\site-packages\ochibaapp.py you can call
gluon.main.wsgibase
Goodluck!
