On Oct 9, 9:30 am, "MerMer" <[EMAIL PROTECTED]> wrote:
> > Your question doesn't really make sense for the development server,
> > since it only ever serves dynamic content.Does this mean that I will have
> > problems serving Javascript files using
> just the development server?
>
No. You can serve pretty much any type of static file with the
development server. This works fine and is very convenient when you are
developing.
As others have appropriately warned, do not do this on a production
site.
You can get the best of both worlds using a conditional clause in your
urls.py.
Here's what I use at the end of my urls.py:
if not settings.PROD_MODE:
urlpatterns += patterns('',
(r'^files/js/(?P<path>.*)$', 'django.views.static.serve',
{'document_root': settings.DEV_JS_ROOT}),
(r'^files/style/(?P<path>.*)$', 'django.views.static.serve',
{'document_root': settings.DEV_CSS_ROOT}),
(r'^files/(?P<path>.*)$', 'django.views.static.serve',
{'document_root': settings.MEDIA_ROOT}),
)
Where it's your responsibility to reset settings.PROD_MODE when you are
developing and to set it when you are in production. Also, DEV_JS_ROOT
and DEV_CSS_ROOT need to be appropriately defined in settings (or
derived from settings.MEDIA_ROOT if that works for you.)
I set my PROD_MODE based on which host my site is running on. For
example, if I know that my production site is going to be running on
prodserver.com, I derive my PROD_MODE like this in settings.py:
import os
PROD_MODE = os.uname()[1].lower().endswith('textdrive.com')
This way, you don't have to worry about modifying settings.py when you
deploy.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
