django,exception,error-handling,django-settings
500 error on production is not something you should make guesses about. You need to know exactly what, where and when is it happening: enable Django Logging and log, log, log set ADMINS configuration setting and receive emails on critical errors ADMINS Default: () (Empty tuple) A tuple that lists...
django,twitter-bootstrap,django-models,django-templates,django-settings
If you store static files in locations other than app/static I think you need to specify STATICFILES_DIRS in your settings.py otherwise they will not be collected: STATICFILES_DIRS = ( "/path/to/static", #collectstatic will find any app/static directories so do not add those here ) By default it is empty. Additionally, specify...
global_settings is, as the name implies, the global default settings supplied by Django. So of course the default is 'auth.User'. Since you override it in your own settings, you should import that instead. But as the documentation says, the way to import the current settings is always from django.conf import...
django's settings should stay immutable. it is supposed to be so. you better create two settings, settings.py, (which is already there) debug_settings.py with DEBUG=True and create two wsgi's in your django. wsgi.py (which is already there) which refers to settings.py wsgi_debug.py which refers to debug_settings.py and in your apache config,...
python,django,crontab,django-settings
I would recommend to put the command in a shell script and then call the program via cron. This way the cron file would look simpler and you could keep the exports in a separate file and then source them in all the other scripts. Example script (run_command.sh) #!/bin/bash DJANGO_SETTINGS_MODULE=myproject.settings...
django,django-settings,django-staticfiles
In DEBUG mode, the Django development server handles serving static files for you. However, this is not best for production as it's much more inefficient than a true server. See here. Serving the files In addition to these configuration steps, you’ll also need to actually serve the static files. During...
python,django,django-authentication,django-settings
make sure it's a tuple: AUTHENTICATION_BACKENDS = ('apps.apployment_site.auth.CustomAuth',) note the comma at the end...
python,django,python-2.7,django-settings
DATABASES option is not configured in settings.py Add this, DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'OPTIONS': { 'read_default_file': '/path/to/my.cnf', }, } } More information is at https://docs.djangoproject.com/en/1.4/ref/settings/...
django,session-cookies,session-timeout,django-settings,django-sessions
Your settings file seems fine. Are you using Gunicorn with multiple workers, If yes than try with single worker only. Actually sessions won't transfer between multiple workers unless you bring some middle layer storage component to it like memcached or redis. Faced same issue some time back. Hope it solves...
python,django,django-templates,django-admin,django-settings
If the error message doesn't seem to match your code, a good step is to remove your *.pyc files and let Python recreate them.
django,django-admin,django-settings
Make sure you have added 'django.contrib.sites' to your INSTALLED_APPS, then run migrate to create the required table. python manage.py migrate ...
django,templates,django-templates,django-settings
I suspect that this error is thrown from django.template.loaders.app_directories.Loader. Try to add TEMPLATE_LOADERS setting: settings.configure( DEBUG=DEBUG, TEMPLATE_DEBUG=True, TEMPLATE_DIRS=( POSTS_DIR, TEMPLATES_DIR, PAGES_DIR, ), TEMPLATE_LOADERS=('django.template.loaders.filesystem.Loader',), ) ...
django,django-settings,django-cache
cache_utils.group_backend is a cache backend that stores data in memcached. By itself it doesn't store it anywhere - on C drive or anywhere else. Memcached also doesn't keep its data on disk, but in memory (RAM). As a consequence there is no right answer to your question. If you want...