Re: apache gets confused with difference between dev and production version of site

On Nov 3, 3:00 pm, Graham Dumpleton wrote: > On Nov 3, 5:55 pm, Stephen Moore wrote: > All I can suggest is get rid of mod_python. It is a fair bit simpler > in mod_wsgi to do these sorts of per setup overrides because the WSGI > script file acts as an intermediary from which overrides can be

apache gets confused with difference between dev and production version of site

Hello, I have a setup where a django's debug setting is changed depending on whether os.environ['PRODUCTION'] is true or false. Which means when I setup apache, I do "SetEnv PRODUCTION true" to mark a site as production. I then have /etc/hosts setup so that http://home and http://cec point to l

creating a list of sql that is executed

Hello, I have a situation where I've created a site using django, using sqlite3. Thus far I've always had the database under version control (which, seeing as it's a binary file, doesn't mean much other than the fact I have a backup) The problem becomes when I make changes on my home computer t

Re: trouble with foreignkey and admin interface

> The error message is telling you exactly what the problem is here. It > wants Position to have a ForeignKey to Member. When you read that and > look at your models and see that you have Member having a ForeignKey to > Position, you have to then think that perhaps that means you've got the > inli

everything works except apache seeing django app

hello. I'm trying out django atm, and I've got it working using the manage.py runserver, but I'm having difficulty making my apache server use it properly, getting the ImportError: Could not import settings problem I have it so that the django app is in my home directory, and I've added an appro