on windows it also was 1.3 I collected statics as you said, but it brought also many not static files Actually all my sources went there.
On 10 August 2011 22:49, Gelonida N <gelon...@gmail.com> wrote: > On 08/10/2011 09:01 PM, Peter Kovgan wrote: > > Ok, Ok, I've got it, read docs. > > > > But why It must be so complex? > > Why default admin statics become unavailable, if you use another server > > and not that of development: "runner"? > > > > Should it mean, that I must find elsewhere my admin statics, copy-paste > > them to some place and poin to this place from settings.py? > > > > OK.... > > I do not like this burden. > > > The burden is not really a big burden. > > Set STATIC_ROOT in config.py to a directory, which is empty and where > you have write permissions to. > > > run afterwards ./manage.py collectstatic > > > This should collect all static files (also the ones from standard django > modules) into the STATIC_ROOT directory. > > If your STATIC_ROOT directory does NOT contain the files that aren't > served, then this is strange. > > > > Just one more question: > > Did you also use Django 1.3 on your windows host or was it a different > version??? > > > > -- > 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 > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
