You are right Marchon, and thank You for your extremely prompt
reaction
In fact I didn't see any resolving issue while requesting from inside
my local network, but from outside there is an issue. I think now it's
solved with a modification to the virtualhost configuration apache
file, where I commented the followin line:
#WSGIApplicationGroup %{GLOBAL}
Thank You again to All of You
kind regards
Daniel
On Aug 2, 8:02 pm, marchon <[email protected]> wrote:
> do you still have a problem to resolve
>
> Sent from my iPhone
>
> On Aug 2, 2009, at 1:55 PM, dani <[email protected]> wrote:
>
>
>
> > George and Damjan,
>
> > First of all, a big Thank to you both for quick and pertinent answers:
>
> > The Issue is SOLVED (thank You again). Werkzeug rocks great (I'll try
> > using more modules from now on). The server is serving great now.
> > Actually I had a couple of issues :
> > - One as You mentioned related to the url resolving mismatch versus
> > the apache directive (this I solved as per George kind suggestion
> > with /etc/hosts local resolution trick)
> > - Another issue was related to the python-path to see modules I put
> > in apache application directory (for this I completed the apache
> > mydomain configuration file with the following line:
> > addressWSGIDaemonProcess mydomain user=theuser group=thegroup
> > processes=1 threads=5 python-path=/var/www/mydomain)
>
> > Finally the working virtualhost configuration apache file for mydomain
> > is:
>
> > <VirtualHost *:80>
> > ServerAdmin [email protected]
> > ServerName mydomain.fr
> > ServerAliaswww.mydomain.fr
>
> > WSGIDaemonProcess mydomain user=theuser group=thegroup
> > processes=1 threads=5 python-path=/var/www/mydomain
> > WSGIScriptAlias / /var/www/mydomain/mydomain.wsgi
>
> > <Directory /var/www/mydomain>
> > WSGIProcessGroup mydomain
> > WSGIApplicationGroup %{GLOBAL}
> > AddHandler wsgi-script .wsgi
> > Order deny,allow
> > Allow from all
> > </Directory>
>
> > ErrorLog /var/log/apache2/error.log
> > LogLevel warn
> > CustomLog /var/log/apache2/access.log combined
> > </VirtualHost>
>
> > Thank You again
> > Daniel
>
> > On Aug 2, 4:17 pm, George Lambert <[email protected]> wrote:
> >> and you must usehttp://mydomain.frforthe wsgiscriptalias to match -
> >> not the ip
>
> >> WRONG -http://192.168.1.19/mydomain because - you are asking the
> >> host to use the IP - not matching the write host directive.
>
> >> WRONG -http://192.168.1.19/mydomain/somethingIgeta 404 - because
> >> you are still not matching the host name
>
> >> RIGHT -http://mydomain.fr/
> >> RIGHT -http://mydomain.fr/residencegrenoble/accueil
>
> >> these will match the domain name - assuming that your domain name IS
> >> actually mydomain.fr and that it resolves on your computer.
>
> >> if your domain name does not resolve on your computer - you may trick
> >> your computer into "LOCAL RESOLUTION" by adding an entry into your
> >> local hosts telling it to resolve the domain to your machine. on a
> >> linux box edit /etc/hosts with a line that looks like this
>
> >> ----------------------------------------
> >> # /etc/hosts
> >> # Host Database
>
> >> 127.0.0.1 mydomain.fr
>
> >> ---------------------------------------
>
> >> On Sun, Aug 2, 2009 at 9:54 AM, Damjan<[email protected]> wrote:
>
> >>> On Aug 2, 11:24 am, dani <[email protected]> wrote:
> >>>> Hello,
>
> >>>> I'm experiencing werkzeug on a simple application (using only
> >>>> template
> >>>> system evoque coupled with werkzeug routing and
> >>>> SharedDataMiddleware).
> >>>> It works perfectly while serving in development environment using
> >>>> werkzeug run_simple.
>
> >>>> I struggled for a couple of days trying running it on apache and
> >>>> mod_wsgi with the instructions athttp://werkzeug.pocoo.org/
> >>>> documentation/dev/deployment/mod_wsgi.html
>
> >>>> Also I've seen posts athttp://groups.google.com/group/pocoo-libs/
> >>>> browse_thread/thread/c944af...
>
> >>>> Unfortunately I could not manage it and I'm not experienced with
> >>>> mod_wsgi, not much with apache. What I see is the following:
> >>>> - When requesting the urlhttp://192.168.1.19/mydomain(withno.xx
> >>>> whatever), I'm served the filesystem view, instead of the home page
> >>>> served trhough the werkzeug application
> >>>> - when requestinghttp://192.168.1.19/mydomain/somethingIgeta 404
> >>>> "The requested URL /residencegrenoble/accueil was not found on this
> >>>> server"
>
> >>>> My apache configs:
> >>>> 1. Virtual host configured
> >>>> 2. /var/www/mydomain contains
> >>>> <VirtualHost *:80>
> >>>> ServerName mydomain.fr
> >>>> WSGIScriptAlias / /var/www/mydomain/mydomain.wsgi
> >>>> <Directory /var/www/rmydomain>
> >>>> AddHandler wsgi-script .wsgi
> >>>> Order deny,allow
> >>>> Allow from all
> >>>> </Directory>
> >>>> ErrorLog /var/log/apache2/error.log
> >>>> LogLevel debug
> >>>> CustomLog /var/log/apache2/access.log combined
> >>>> </VirtualHost>
>
> >>> Why don't you use WSGIScriptAlias ? It's much more straight forward
>
> >> --
> >> P THINK BEFORE PRINTING: is it really necessary?
>
> >> This e-mail and its attachments are confidential and solely for the
> >> intended addressee(s). Do not share or use them without approval. If
> >> received in error, contact the sender
> >> and delete them.
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pocoo-libs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pocoo-libs?hl=en
-~----------~----~----~----~------~----~------~--~---
