On Aug 22, 1:58 am, MilesTogoe <[EMAIL PROTECTED]> wrote:
> Florian Apolloner wrote:
> > Of course you are right, the NameVirtualHost is in another file, so
> > the snippet doesn't include it. But my config works, just wanted to
> > show it to Miles.
>
> I appreciate your post, however, the webfaction shared hosting does not
> seem set up to do virtual hosting in that manner - the support team at
> webfaction was nice enough to get my config file working to serve up the
> .wsgi file. However, it was still not serving the the application or
> views file correctly and not showing any clues in the error file. I see
> the problem as trying to integrate 3 pieces -mod_wsgi, webfaction's
> hosting setup, and werkzeug. We are more application developers and not
> knowledgeable enough on sysadmin or wsgi to get this working without a
> real step by step tutorial which there seems none. And comments like
> "rtfm" on irc don't really help much. So at this point we're falling
> back to using Rails to have stuff running and will experiment with
> werkzeug/python as we can.
I would have stepped in and provided guidance, however your
descriptions as to the problem were quite inadequate. If you want help
you need to help yourself to the extent of providing as much
information as possible. Without such information all one can do is
look into a crystal ball and guess.
So, maybe you want to try again, but this time provide better
information. Start with your Apache configuration, but more
importantly indicate what URL you are then accessing, the exact
details of any error response you are getting displayed in your
browser, any corresponding error messages from the Apache error log
etc etc. Don't just assume something isn't relevant as minor details
can say a lot about what a problem is.
BTW, also ensure that you have set:
LogLevel debug
in Apache configuration. That is, override the default of 'warn'. This
will cause mod_wsgi to output more information to error log files.
Also ensure you have an error log configured to begin with. I don't
recollect your original configuration even showing the ErrorLog
directive. If it is at global scope fine, but can't tell at moment if
set or not.
Maybe with all this information we may be able to actually work out if
you are complaining if mod_wsgi is not working or if your WSGI
application is not working. Right now it isn't too clear.
Graham
> > On Aug 17, 11:28 pm, "George Lambert" <[EMAIL PROTECTED]> wrote:
>
> >> are you missing a namedvirtualhost tag at the top of the apache config file
>
> >> if you are missing the declaraion at the top of the file the virtual
> >> host entry will not be processed.
>
> >> to access the script you will need to be using an http rquest that
> >> matches the named virtual host
>
> >> and if the virtual host is being used properly then there will be log
> >> entries in the virtual host specific access and error logs
>
> >> check that they have entries, and then post back the last few wlines
> >> of what is in them
>
> >> On 8/17/08, Florian Apolloner <[EMAIL PROTECTED]> wrote:
>
> >>> That's my full setup (on a test server):
> >>> <VirtualHost *:80>
> >>> ServerName staging.tld.eu
>
> >>> WSGIDaemonProcess staging user=web group=web processes=2 threads=1
> >>> maximum-requests=500
> >>> WSGIProcessGroup staging
> >>> WSGIScriptAlias / /home/web/conf/apache/staging.wsgi
>
> >>> <Directory /home/web/conf/apache>
> >>> # WSGIApplicationGroup %{GLOBAL} # Use this if running in
> >>> embedded mode and not in the process setup like I use in this example.
> >>> Order deny,allow
> >>> Allow from all
> >>> </Directory>
>
> >>> </VirtualHost>
>
> >>> On Aug 17, 8:29 pm, MilesTogoe <[EMAIL PROTECTED]> wrote:
>
> >>>> Florian Apolloner wrote:
>
> >>>>> Hi, You will need to open access for the directory containing the wsgi
> >>>>> file, eg (a really simple setup I am using...):
>
> >>>>> WSGIScriptAlias / /home/web/conf/apache/app.wsgi
>
> >>>>> <Directory /home/web/conf/apache> # this is the same dir as mentioned
> >>>>> by WSGIScriptAlias
> >>>>> Order deny,allow
> >>>>> Allow from all
> >>>>> </Directory>
>
> >>>>> (Btw there is no need to have your wsgi files inside of your
> >>>>> ServerRoot). That's all what I can say now, without complete
> >>>>> description of your error or access to the necessary logfiles. See
> >>>>>http://code.google.com/p/modwsgi/wiki/ConfigurationGuidelinesformore
> >>>>> pointers. If you still can't enable it ping me on freenode (apollo13,
> >>>>> mostly on #pocoo too).
>
> >>>> Thanks, but the site still doesn't seem to be accessing the .wsgi
> >>>> file. A "recommended" directory structure and matching apache config
> >>>> example would be very helpful
>
> >>>>> On Aug 16, 8:40 pm, MilesTogoe <[EMAIL PROTECTED]> wrote:
>
> >>>>>> our setup on shared hosting is not working (we are gettingmod_wsgi-
> >>>>>> but not pointing to our app)
> >>>>>> here is the apache httpd.conf
> >>>>>> ServerRoot "/home/user/webapps/ourapp/apache2"
>
> >>>>>> LoadModule dir_module modules/mod_dir.so
> >>>>>> LoadModule env_module modules/mod_env.so
> >>>>>> LoadModule log_config_module modules/mod_log_config.so
> >>>>>> LoadModule mime_module modules/mod_mime.so
> >>>>>> LoadModule rewrite_module modules/mod_rewrite.so
> >>>>>> LoadModule wsgi_module modules/mod_wsgi.so
>
> >>>>>> DirectoryIndex index.py
> >>>>>> DocumentRoot /home/user/webapps/ourapp/htdocs
> >>>>>> Listen 7061
> >>>>>> LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\"
> >>>>>> \"%{User-Agent}i\"" combined
> >>>>>> CustomLog logs/access_log combined
> >>>>>> ServerLimit 2
> >>>>>> WSGIScriptAlias / /home/user/webapps/ourapp/ourapp.wsgi
>
> >>>>>> <Directory /home/user/webapps/ourapp/htdocs>
> >>>>>> AddHandler wsgi-script .py
> >>>>>> </Directory>
>
> >>>>>> and here is ourapp.wsgi file
> >>>>>> from ourapp import models, utils
> >>>>>> from ourapp.application import OurApp
> >>>>>> application = OurApp('sqlite:///ourapp/ourapp.db')
>
> >>>>>> any thoughts why it's not working correctly ?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
