Sorry to re-awaken this thread, but it seems that people are still
having issues with this PYTHONPATH info. In an attempt to get this
sorted out, I've attached a patch to #4296 that adds a bit more info.
Can anyone add any more info to what I've got?
Thanks,
Simon G
#4296 -
Graham Dumpleton wrote:
> On Jul 6, 2:59 pm, John-Scott <[EMAIL PROTECTED]> wrote:
>> On Jul 6, 12:29 am, Graham Dumpleton <[EMAIL PROTECTED]>
>> wrote:
>>
>>> Hmmm, I'm not sure the documentation is actually accurate. When you
>>> use manage.py to run up development server for Django, it will
Maybe an example would be useful as well:
== Apache conf file ===
ServerName site.com
ServerAdmin [EMAIL PROTECTED]
DocumentRoot /home/user/django/site
SetHandler python-program
PythonPath "['/home/user/django'] + sys.path"
PythonHandler
On Jul 6, 2:59 pm, John-Scott <[EMAIL PROTECTED]> wrote:
> On Jul 6, 12:29 am, Graham Dumpleton <[EMAIL PROTECTED]>
> wrote:
>
> > Hmmm, I'm not sure the documentation is actually accurate. When you
> > use manage.py to run up development server for Django, it will
> > automatically add the
On 7/5/07, John-Scott <[EMAIL PROTECTED]> wrote:
> In my settings.py, I now have:
> MEDIA_ROOT = '/var/www/mysite.com/media/'
> MEDIA_URL = 'http://mysite.com/media/'
> ADMIN_MEDIA_PREFIX = '/media/'
Err, I don't have my code or settings file handy. This is the kind
of thing you forget, since
On Jul 6, 12:29 am, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> Hmmm, I'm not sure the documentation is actually accurate. When you
> use manage.py to run up development server for Django, it will
> automatically add the parent directory of where the manage.py file is
> located into sys.path
On Jul 6, 1:24 pm, John-Scott <[EMAIL PROTECTED]> wrote:
> @Vincent - Is specifying the path necessary because I'm using the
> development version of django and not an official installer? In the
> official docs it says you only have to specify the path "if you've
> manually altered your
On 7/5/07, John-Scott <[EMAIL PROTECTED]> wrote:
> (i.e. MEDIA_ROOT, MEDIA_URL, ADMIN_MEDIA_PREFIX) are
> supposed to interact with the Apache config. back to the docs...
MEDIA_ROOT is used for uploads (like FileField and ImageField.
MEDIA_URL should be the service URL matching MEDIA_ROOT; it is
On Jul 5, 11:33 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> You want to have the 'django_src' directory linked onto your Python
> path, not the 'django' directory -- the Python path should contain the
> *parent* directories of any modules you want Python to be able to
> find.
According to
On 7/5/07, John-Scott <[EMAIL PROTECTED]> wrote:
> @Nimrod - You were right about the permissions on /home/john-scott/
> workspace, chmod 755 fixed that. But I still have to have the django
> development code in /opt to get it to load. Any ideas why symlinking
> to
Thanks for the prompt replies.
@Nimrod - You were right about the permissions on /home/john-scott/
workspace, chmod 755 fixed that. But I still have to have the django
development code in /opt to get it to load. Any ideas why symlinking
to /home/john-scott/workspace/django_src/django doesn't
Try adding the following in the location block:
PythonPath "['/home/john-scott/workspace'] + sys.path"
Vincent
On 7/5/07 9:03 PM, "John-Scott" <[EMAIL PROTECTED]> wrote:
>
> Hello all,
>
> I'm having some issues getting a basic django project in production
> mode.
>
> I'm using Ubuntu
Hello,
Your problem could be that the permissions to /home/john-scott do not
allow directory traversal down into this directory for "other" users.
You probably need to do:
$ chmod 0755 /home/john-scott
$ chmod 0755 /home/john-scott/workspace
$ cd /home/john-scott/workspace
$ find -type d |
Hello all,
I'm having some issues getting a basic django project in production
mode.
I'm using Ubuntu 6.06 LTS with the default versions of apache, python,
mod_python, etc.
- I've checked out the development version of Django in my home
directory, i.e. /home/john-scott/workspace/django_src and
14 matches
Mail list logo
