You can use Django to serve your CSS file if you want to, although you'll want to cache the heck out of it for performance reasons. There are also a wide variety of tools which generate CSS from various input files to allow for various kind of template expansion, and those might be a suitable alternative.
--
-- Christophe Pettus
x...@thebuild.com
2012/1/2 Christophe Pettus <x...@thebuild.com>:
> --
> You received this message because you are subscribed to the Google Groups "Django users" group.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to django-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
>
--
Andrés Reyes Monge
arm...@gmail.com
+(505)-8873-7217
The worse way is to serve your static files as views, complete with template
rendering. This will be even morepainful if you use Django templates as the
templating engine, since you will have to quote all those braces that you need
in CSS and Javascript. You might find a templating scheme that fits the task
better, and feed it the variable values you need to.
The bad way is like the worse way, but is more work: you do the same template
interpolation, but from a management command, which makes versions of your
static files with all substitutions applied, and which places them in
the folder from
which your front end apache or ngniz will really serve them, which
should probably
be where runserver will look for them as well. You would have to remember to
run this when you changed something.
Bill
> This will be even morepainful if you use Django templates as the
> templating engine, since you will have to quote all those braces that you need
> in CSS and Javascript.
I don't believe this is correct; Django's templating engine doesn't choke on single braces.