Ok, that makes sense now but only concerns me more because logging in
daemon mode is not working, using wsgi.errors or sys.stderr. However,
I'm a bit confused because CustomLog is used for access logs, which
does work btw if I wasn't clear. It's only error logs that don't work.
-jeff
On Dec 19,
I am only referring to anything output directly via sys.stderr.
Any messages output via wsgi.errors passed in the WSGI environment,
which is how most WSGI application would tend to log, would go to the
log file associated with the context the request is handled in. If you
have a CustomLog in a Vi
That doesn't seem to be the case. We're using this inside our VirtualHost:
ErrorLog /path/to/error_log
CustomLog /path/to/access_log combined
We're looking at the error_log file for this vhost and in embedded
mode we *do* see Pylons errors when raised but in daemon mode we do
not, which seems th
Which Apache error log file are you looking in? Do you have
VirtualHost specific CusomLog defined?
When run in mod_wsgi daemon mode, the sys.stderr output will be
redirected to a VirtualHost specific error log file if
WSGIDaemonProcess was defined in the context of the VirtualHost.
When in mod_w
Hey Graham,
Actually, I thought I was having the same issue since I was getting no
logging at all from Pylons when using mod_wsgi. However, after trying
this and it not working, it looks like it has to do with using
mod_wsgi in daemon mode. (No, not on FreeBSD this time). I can seem to
log from t
Hi Lythoner,
You've spotted the SQLAlchemy 0.4 driver have you? AuthKit has never
used SAContext ever.
Cheers,
James
Lythoner LY wrote:
> Enrico,
>
> AuthKit 0.4 is not updated to use the full power of sqlalchemy 0.4. I
> had faced a lot of issues with UsersFromDatabase class last week.
The following seems to work:
app = middleware(
app,
app_conf=app_conf,
setup_method='cas',
cas_authority = 'https://cashost:8443/cas/',
cas_protect='/login' # paths starting with /
login are protected
)
or e
