On May 19, 2012, at 9:58 AM, Marian Siwiak wrote: > Ok. That was helpful. Probably problem is with configuration in > /etc/apache2/sites-available > > one question - online book says to make special web2py file, while cookbook > says to modify default file. > neither of 2 approaches seem to work... is there anything wrong with those > examples they presented?
Either way should work, as long as sites-enabled is linked to the right one. It depends on your overall configuration and how you have virtual servers set up, but in the simplest case you don't want sites-enabled to link to both web2py and default configurations, because they're likely to be in conflict. I'm guessing that your other problem is related to telling Apache which URLs are to be handled by mod_wsgi and/or pointing mod_wsgi to the right path to the handler. > > Marian > > W dniu sobota, 19 maja 2012 18:41:04 UTC+2 użytkownik Niphlod napisał: > it seems that apache doesn'0t understand to pass page rendering to mod_wsgi > and instead offers the default behaviour (list and send file). > > Without further details it's quite impossible make some other assumptions... > > Il giorno sabato 19 maggio 2012 17:28:26 UTC+2, Marian Siwiak ha scritto: > Hello again, > > I have a problem with deploying my application. > I have set up apache2 server with mod_wsgi on my machine (It runs on debian > 6.0.4). > The change I made was to use /var/ww instead of /users/www-data folder. > Everything went smoothly, as described in web2py online book, but when typing > www.myserver.pl/path/to/my/application in my browser I get a list of files > instead of application index page. Any suggestions where to search for the > problem (except PEBCAK)? > > best regards and thanks in advance, > Marian
