I tried with it, reverted back to another one...
Just for the sake of testing it, I've tried it, and still no luck.
My apache cfg is noe
<VirtualHost *:80>
ServerName aec.dev
ServerAlias www.aec.dev
serverAlias tmain.ath.cx
DocumentRoot /var/www/arc_en_ciel/htdocs/
CustomLog /var/www/arc_en_ciel/log/access_log combined
ErrorLog /var/www/arc_en_ciel/log/error_log
RewriteEngine on
RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK)
RewriteRule .* - [F]
include /etc/apache2/vhosts.d/expire
include /etc/apache2/vhosts.d/defRoot
#setEnv LOCATION dev
#php_admin_value auto_prepend_file /var/www/arc_en_ciel/htdocs/libs/
prepend/prepend.php
#php_admin_value auto_append_file /var/www/arc_en_ciel/htdocs/libs/
append/append.php
#php_admin_value error_log /var/www/arc_en_ciel/log/php.log
#php_admin_flag display_errors 1
#php_admin_flag log_errors 1
WSGIDaemonProcess tmain.ath.cx processes=2 threads=15 display-name=%
{GROUP}
WSGIProcessGroup tmain.ath.cx
WSGIScriptAlias / /var/www/arc_en_ciel/htdocs/base.py
</VirtualHost>
> > So, when you claim that permissions on directory where database is
> > correct, what does that mean?
> The directory and the sqlite db are chmoded to 664 and the owner of
> both directory and db is apache:webdev
> Which isn't what your 'ls' output below says. A directory would never
> be 664 as it would block directory search.
True, I've spotted it after sending the message, and had chmodded the
whole path to 777, for testing.
But still, it was the same.
> Anyway, all academic now if you have gone back to PHP.
Not at all. I have not totally ditched web.py, but I need to have
something running in the next days, and I cannot waste more time on a
configuration problem.
I cannot replace apache with lighthttpd neither, as I have many sites
running now on the future server, and I won't go in the hassle of
updating them all just for that.
I thought about running a second webserver on a different port, but
not for now.
The point is, that even with the bare session demo of web.py 0.3 and
following the recommanded setup of apache+mod_wsgi, it don't work.
I now have spent around 15 hours to try to have it working in apache,
for around 5 hours of development.
So, my quetion could be trivial, but does anyone have ever tried to
use the sessions on an web.py 0.3 on apache with mod_wsgi with the
recommanded settings?
Maybe it's my apache configuration, maybe it's my wsgi directives,
maybe it's my python install. I have absolutely no clues.
I've reinstalled apache, tried worker and prefork mpm's.
I've tried to install other session middleware, I've downgraded
web.py. mod_wsgi and apache, and nothing have made it working.
I've even tested the script on 3 servers, the same results on the 3.
My impression is that the session object is only attached to the
web.py object, not the wsgi object.
If I try to attache it to the wsgi object, I've got an error telling
me:
AttributeError: 'function' object has no attribute 'add_processor'
At this point, I stopped trying, and switched to PHP.
But this saddens me...
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web.py" 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/webpy?hl=en
-~----------~----~----~----~------~----~------~--~---
