Graham Dumpleton wrote:
> 2008/11/28 MilesTogoe <[EMAIL PROTECTED]>:
>   
>>>> hmm, I'll check on the permissions
>>>>
>>>>         
>>>>> Are you running mod_wsgi embedded mode or daemon mode? If daemon mode,
>>>>> are you setting user/group for process to one that has adequate
>>>>> privileges over directory where database is.
>>>>>
>>>>>
>>>>>           
>>>> I have no idea of embedded vs daemon.  I'm using a stock setup from
>>>> webfaction - is there a way I can tell ?  in the httpd.conf I have:
>>>>
>>>>         
>>> WebFaction is embedded mode unless you override it, but believe the
>>> Apache instance runs as your user anyway. Thus permissions probably
>>> not the problem, but not using as absolute path would be.
>>>
>>>       
>> okay, but now I've tried just about every combination of absolute paths
>> I can think of with the same error - wondering if there is a way that
>> the path it is searching for can be reported ?  maybe that's an
>> sqlalchemy issue but if someone knows it would be helpful.
>>     
>
> Just a thought, but does anyone know what are the requirements these
> days in respect of multithread and/or multiprocess access to sqlite
> database?
>
> If WebFaction using worker MPM for Apache, would have potentially
> multiple processes and multiple threads in process trying to use it.
> That may not be safe.
>
> Can you use PostgreSQL instead?
>   
well, it is probably a very good suggestion to use postgres but we like 
to use sqlite to get going fast on a new project, especially with lots 
of development underway.   

Anyway the good news - turns out I just needed to restart the server 
between .wsgi file changes (only thought I had to do that with conf 
changes).   So we now have a cool Werkzeug stack (mod_wsgi, Werkzeug, 
SQLAlchemy, Jinja) framework deployed on Webfaction.   We have tried 
most frameworks and I think this is the best overall stack there is.   
I'll be writing up a tutorial on this.  thks so much for all your help.  
We will also detail the steps to get it running on a VPS which should be 
fairly easy now.  And we will use postgres.  

Next we're onto integrating auth and sessions middleware - oh that 
should be a challenge. 


> Graham
>
> >
>
>   


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"modwsgi" 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/modwsgi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to