Thanks for the advices. But sadly, it's not that. The sqlite parent folder perms are ok. After that mail, I created a "log" table, and made the script write it something on the first page loading, and it appears. Only the sessions table stay empty.
Again, if run it from the webpy server, the sessions appears in the session table, and everything works. I'm stumbled... On Mar 25, 4:19 am, Graham Dumpleton <[email protected]> wrote: > On Mar 25, 2:11 pm, Brent Pedersen <[email protected]> wrote: > > > sqlite needs write permissions on the _directory_ > > where the sqlite database is located and (r/write permissions) > > on the file itself. > > > so after defining try: > > > assert os.path.exists(self.finalDb), "db doesnt exist" > > assert os.access(self.finalDB, os.W_OK), "cant write to db file" > > assert os.access(self.dbPath, os.W_OK), "cant write to db directory" > > > and see which on fails. then adjust permissions. > > However, don't just go making the directories world writable. You are > better off running mod_wsgi daemon mode and run your application as > distinct user from Apache user, perhaps even yourself, such that it > has same access rights as yourself and can use the directories without > having to make them world writable or make the directories owned by > Apache user. > > Also double check that your configuration isn't using a relative path > to stuff like the database. In Apache the current working directory > could be anything. > > Graham --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
