On Tue, Jul 20, 2010 at 1:49 AM, MatthewHoopes <[email protected]> wrote:
> 19:46:04,889 INFO [scgi-wsgi] GET /hello/index
> /usr/local/lib/python2.6/dist-packages/flup-1.0.3.dev_20100221-py2.6.egg/flup/server/scgi_base.py:536:
> DeprecationWarning: Configured SCRIPT_NAME is deprecated
> Do not use WSGI_SCRIPT_NAME or the scriptName
> keyword parameter -- they will be going away
>
> Is there a new param I should be worried about?
I did a little research and found that this could be fixed with
setting "fix-root-scriptname" (enable) in the lighttpd configuration
file, but keep in mind that this option is available only since
version 1.4.23. Read more on
http://redmine.lighttpd.net/projects/lighttpd/wiki/Docs:ModFastCGI
(http://redmine.lighttpd.net/projects/lighttpd/wiki/Docs:ModSCGI
claims that "The SCGI module is heavily based on the FastCGI when it
comes to configuration. (...) Please check the documentation of the
FastCGI module for more information.")
> Since I'm running paster on port 6500, and lighttpd is simply a proxy for
> that...what's the point of the document root line?
>
Well, in my opinion, You could leave that option not set.
Here is my full working config (ubuntu 10.04, lighttpd
1.4.26-1.1ubuntu3, pylons 1.0):
/etc/lighttpd/conf-available/10-scgi.conf:
server.modules += ( "mod_scgi" )
scgi.server = ( "/" =>
((
"host" => "127.0.0.1",
"port" => 6500,
"check-local" => "disable",
"fix-root-scriptname" => "enable"
))
)
development.ini:
[server:main]
use = egg:Flup#scgi_thread
host = 127.0.0.1
port = 6500
To turn the scgi on, You could invoke `$ lighty-enable-mod scgi` or
simply `$ ln -s /etc/lighttpd/conf-available/10-scgi.conf
/etc/lighttpd/conf-enabled/`. Remeber to restart lighttpd afterwards:
`invoke.rc.d lighttpd force-reload`. Hope that helps!
Why don't You use FastCGI?
--
Yours sincerely,
Jakub Warmuz
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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/pylons-discuss?hl=en.
