Re: Deploying with Apache: confused by odd PythonPath requirement

2009-09-14 Thread Mark (Nosrednakram)
Hello Dan, CAUTION: I don't think the is the standard way of doing this but I have found it to make my code portable and easy to implement. Your mileage may very but I have started removing the project name from all of my code and for this configuration to work you would need to also. I use the

Re: Deploying with Apache: confused by odd PythonPath requirement

2009-09-13 Thread Graham Dumpleton
On Sep 14, 7:31 am, Dan06 wrote: > I've 'successfully' deployed django in a development environment on > Apache2. While, I've got it to work, I'm > thoroughly confused by the PythonPath setting needed for it to work. > > I don't understand why I need to give the directory that contains the > dj

Deploying with Apache: confused by odd PythonPath requirement

2009-09-13 Thread Dan06
I've 'successfully' deployed django in a development environment on Apache2. While, I've got it to work, I'm thoroughly confused by the PythonPath setting needed for it to work. I don't understand why I need to give the directory that contains the django 'project' AND the directory that contains