I have a similar problem. My STATIC_URL is a full URL like http://static.mysite.com. When I use the development server with runserver, django *always* takes this URL. In the templates I use {{STATIC_URL}}/myimage.jpg, and in development I always see http://static.mysite.com/myimage.jpg in my browser. When I add a static file in development it doesn't yet exist in the production static server...
I couldn't find a way to fix this, except serving my static files at www.mysite.com/static/ instead of http://static.mysite.com. But this is just a workaround and no solution to the rpoblem for me. Maybe anyone has an idea. Am Montag, 14. Mai 2012 15:29:07 UTC+2 schrieb Reinout van Rees: > > On 11-05-12 08:48, e.generalov wrote: > > ps: but why these restrictions are needed in the tool, which should > > assist in the development? > > I think you're using it in a strange way, as I (nor anyone I know that > uses django-staticfiles) has any problem in development. > > You said in a reply to one of my messages something about "needing a > full path name '/tmp/....' for saved pages". What did you mean by that? > Such a full path is different from a proper localhost:8000 url. > > > Reinout > > -- > Reinout van Rees http://reinout.vanrees.org/ > rein...@vanrees.org http://www.nelen-schuurmans.nl/ > "If you're not sure what to do, make something. -- Paul Graham" > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/IFRod3AkcCQJ. To post to this group, send email to django-users@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.
