Re: Tutorial

On Apr 21, 8:59 am, Gerald Klein <j...@zognet.com> wrote:
> I guess the problem I am having at this point is that the css files for
> admin are generated dynamically and I don't know where from as far as what
> the path should be that I could map it. I tried setting up the static
> mapping but I don't know what to point to as it's root.

No, it's not dynamically generated. Most django app will have static
files in their <app_dir>/static or for older app that does not yet
follow > 1.3 convention, they'll place their static files in <app_dir>/
media. You then need to collect all the static files for each app and
place it somewhere that your web server can serve it. If using apache,
you can put it under DocumentRoot of your vhost or set proper alias to
the directory where you collect all the static files in one place
(STATIC_ROOT). You don't have to do this manually since django > 1.3
provide app name staticfiles if enabled in your INSTALLED_APP provide
some helper command to collect all the static files into one place.
The doc explain this better.

If you want to do it manually, then just go through each of your
install app looking for directory name 'static'. For django admin as
an example:-

$ python
>> import django
<module 'django' from '/home/kamal/lib/python2.6/site-packages/
Django-1.3.1-py2.6.egg/django/__init__.pyc'>

Now I know to find the static for admin in /home/kamal/lib/python2.6/
site-packages/Django-1.3.1-py2.6.egg/django/contrib/admin/static.

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.