This is kind of an aside to your question, but I think you'll find it
useful...

There are two types of static media that you'll want to have served
separately to your dynamic django application:

* project static media
* uploaded media

I like to keep these two separate. My preferred way to do this is to
use STATIC_ROOT/STATIC_URL for the project static media, retaining the
default MEDIA_* settings for uploaded media only.

When using the built-in development server, it is fine to use it to
serve your static media. When you shift to a full webservice stack,
for your static media you'll make your web service bypass the django
wsgi app or use a seperate web service altogether.

One final catch is when you need to develop a stand-alone apps which
needs to have its own media files.

A nice solution to serving all the your static media easily in the dev
server, and collating all your app's static media to a single location
is http://bitbucket.org/jezdez/django-staticfiles/src

On Jul 15, 2:33 am, reduxdj <patricklemi...@gmail.com> wrote:
> I want to use ImageField for users to upload static content and I need
> a little advice from a some django pros on how to do this in a dev
> enviornment. I notice the disclaimer that django dev server should not
> used to serve static content, or it shouldn't be.  So...
>
> What's the best practice for this then?
> Right now, I love the simplicity of the django dev webserver, should i
> switch the devserver to nginx?
> Does that have the ability to know when i make a change to a python
> file without a server restart necessary?
> Is there anything else I should know.
>
> Thanks so much,
> Patrick

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to