Also the /admin/ url gives
> an internal error, which in apache's errlog shows a traceback
> that ends in "OperationalError: no such table: django_session".
This is most probably due to the fact that you did not set your
DB_NAME variable with the full path of your .db file. And sqlite3 is
creating a new .db file as it cannot access the real one.
That is:
Instead of
DATABASE_NAME = 'dev.db'
you should set it as
DATABASE_NAME = '/path/to/db/file/mydbfile.db'
And for the vhost configuation let me write down what works for me:
ServerName www.mysite.com
ServerAlias *mysite.com
Alias /media/admin /usr/lib/python2.5/site-packages/django/contrib/
admin/media
<Location /media/admin>
Order allow,deny
Allow from all
</Location>
Alias /media /path/to/project/site_media
<Location /media>
Order allow,deny
Allow from all
</Location>
WSGIScriptAlias / /path/to/project/apache/my.wsgi
WSGIDaemonProcess mysite.com user=myuser group=www-data threads=25
WSGIProcessGroup mysite.com
And set the configuration variables accordingly as:
MEDIA_ROOT = '/path/to/project/site_media/' #this is for file
uploads
MEDIA_URL = "http://mysite.com/media/";
ADMIN_MEDIA_PREFIX = '/media/admin/'
> (I also have MEDIA_ROOT set -- is it necessary to have both??)
Yes it is. At least in this configuration I am demonstrating.
Hope this helps.
Regards,
Polat Tuzla
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" 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/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
