معرفی شرکت ها
django-static-1.5.6
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشترتوضیحات
Template tags for better serving static files from templates in Django
| ویژگی | مقدار |
|---|---|
| سیستم عامل | - |
| نام فایل | django-static-1.5.6 |
| نام | django-static |
| نسخه کتابخانه | 1.5.6 |
| نگهدارنده | [] |
| ایمیل نگهدارنده | [] |
| نویسنده | Peter Bengtsson |
| ایمیل نویسنده | mail@peterbe.com |
| آدرس صفحه اصلی | https://github.com/peterbe/django-static |
| آدرس اینترنتی | https://pypi.org/project/django-static/ |
| مجوز | BSD |
About django-static
===================
.. contents::
What it does
------------
``django_static`` is a Django app that enables as various template tags
for better serving your static content. It basically rewrites
references to static files and where applicable it does whitespace
optmization of the content. By making references to static content
unique (timestamp included in the name) you can be very aggressive
with your cache-control settings without ever having to worry about
upgrading your code and worrying about visitors using an older version.
The five template tags it enables are the following:
1. ``staticfile`` Takes the timestamp of the file, and makes a copy by
symlinking as you define. You use it like this::
<img src="{% staticfile "/images/foo.png" %}"/>
and the following is rendered::
<img src="/images/foo.123456789.png"/>
...assuming the epoch timestamp of the file is 123456789.
2. ``slimfile`` Works the same as ``staticfile`` but instead of copying
the file as a symlink it actually rewrites the file and compresses
it through `slimmer <https://pypi.python.org/pypi/slimmer/>`__. This of
course only works for ``.js`` and ``.css`` files but it works
wonderfully fast and is careful enough to not break things. The
cool thing about doing this for ``.css`` files it finds all relative
images inside and applies ``staticfile`` for all of them too. You use
it just like ``staticfile``::
<script type="text/javascript"
src="{% slimfile "/javascript/myscript.js" %}"></script>
3. ``slimcontent`` is used to whitespace compress content right in the
template. It requires a format parameter which can be ``"js"``,
``"css"`` or ``"html"``. So, for example for some inline CSS content
you do this::
<style type="text/css">
{% slimcontent "css" %}
h1, h2, h3 {
font-face: 'Trebuchet MS', Verdana, Arial;
}
{% endslimcontent %}
</style>
...and you get this::
<style type="text/css">
h1,h2,h3{font-face:'Trebuchet MS',Verdana,Arial}
</style>
4. ``staticall`` combines all files between the tags into one and
makes the same symlinking as ``staticfile``. Write this::
{% staticall %}
<script src="/javascript/foo.js"></script>
<script src="/javascript/bar.js"></script>
{% endstaticall %}
...and you get this::
<script src="/javascript/foo_bar.123456789.js"></script>
5. ``slimall`` does the same compression ``slimfile`` does but also
combines the files as ``staticall``. Use it like ``staticall``::
{% slimall %}
<script src="/javascript/foo.js"></script>
<script src="/javascript/bar.js"></script>
{% endslimall %}
``staticall`` and ``slimall`` fully support ``async`` or ``defer``
JavaScript attributes. Meaning this::
{% slimall %}
<script defer src="/javascript/foo.js"></script>
<script defer src="/javascript/bar.js"></script>
{% endslimall %}
...will give you this::
<script defer src="/javascript/foo_bar.123456789.js"></script>
Be careful not to mix the two attributes within the same blocks
or you might get unexpected results.
Configuration
-------------
``django_static`` will be disabled by default. It's not until you set
``DJANGO_STATIC = True`` in your settings module that it actually starts
to work for you.
By default, when ``django_static`` slims files or makes symlinks with
timestamps in the filename, it does this into the same directory as
where the original file is. If you don't like that you can override
the save location by setting
``DJANGO_STATIC_SAVE_PREFIX = "/tmp/django-static"``
If you, for the sake of setting up your nginx/varnish/apache2, want
change the name the files get you can set
``DJANGO_STATIC_NAME_PREFIX = "/cache-forever"`` as this will make it easier
to write a rewrite rule/regular expression that in
nginx/varnish/apache2 deliberately sets extra aggressive caching.
Another option is to let django_static take care of setting your
``MEDIA_URL``. You could do this::
<img src="{{ MEDIA_URL }}{% staticfile "/foo.png" %}"/>
But if you're feeling lazy and what django_static to automatically
take care of it set ``DJANGO_STATIC_MEDIA_URL``. In settings.py::
DJANGO_STATIC_MEDIA_URL = "//static.example.com"
In your template::
<img src="{% staticfile "/foo.png" %}"/>
And you get this result::
<img src="//static.example.com/foo.1247785534.png"/>
Right out of the box, ``DJANGO_STATIC_MEDIA_URL`` will not be active
if ``DJANGO_STATIC = False``. If you want it to be, set
``DJANGO_STATIC_MEDIA_URL_ALWAYS = True``.
By default django_static will look for source files in ``MEDIA_ROOT``,
but it is possible tell django_static to look in all directories listed
in ``DJANGO_STATIC_MEDIA_ROOTS``. The first match will be used.
There is also a setting ``DJANGO_STATIC_USE_SYMLINK`` that can be set to
``False`` to force django_static to copy files instead of symlinking them.
Advanced configuration with DJANGO_STATIC_USE_MANIFEST_FILE
-----------------------------------------------------------
If you enable, in your settings, a variable called
``DJANGO_STATIC_USE_MANIFEST_FILE`` you can save filenames to
manifest.json which is stored in the first match directory in
``DJANGO_STATIC_MEDIA_ROOTS``. This is for the usecase where we want to
manually upload css and javascript files to CDN. On production, where DEBUG=False,
django-static will pick the filenames from manifest.json file instead of
doing all the calculations.
Advanced configuration with DJANGO_STATIC_FILE_PROXY
----------------------------------------------------
If you enable, in your settings, a variable called
``DJANGO_STATIC_FILE_PROXY`` you can make all static URIs that
``django_static`` generates go though one function. So that you, for
example, can do something with the information such as uploading to a
CDN. To get started set the config::
DJANGO_STATIC_FILE_PROXY = 'mycdn.cdn_uploader_file_proxy'
This is expected to be the equivalent of this import statement::
from mycdn import cdn_uploader_file_proxy
Where ``mycdn`` is a python module (e.g. ``mycdn.py``) and
``cdn_uploader_file_proxy`` is a regular python function. Here's the
skeleton for that function::
def cdn_uploader_file_proxy(uri, **kwargs):
return uri
Now, it's inside those keyword arguments that you get the juicy gossip
about what ``django_static`` has done with the file. These are the
pieces of information you will always get inside those keyword
argments::
new = False
checked = False
changed = False
notfound = False
The names hopefully speak for themselves. They become ``True`` depending
on what ``django_static`` has done. For example, if you change your
``foo.js`` and re-run the template it's not ``new`` but it will be ``checked``
and ``changed``. The possibly most important keyword argument you might
get is ``filepath``. This is set whenever ``django_static`` actually does
its magic on a static file. So, for example you might write a function
like this::
on_my_cdn = {}
def cdn_uploader_file_proxy(uri, filepath=None, new=False,
changed=False, **kwargs):
if filepath and (new or changed):
on_my_cdn[uri] = upload_to_my_cdn(filepath)
return on_my_cdn.get(uri, uri)
Advanced configuration with DJANGO_STATIC_FILENAME_GENERATOR
------------------------------------------------------------
By default, django-static generates filenames for your combined files
using timestamps. You can use your own filename generating function
by setting it in settings, like so::
DJANGO_STATIC_FILENAME_GENERATOR = 'myapp.filename_generator'
This is expected to be the equivalent of this import statement::
from myapp import filename_generator
Where ``myapp`` is a python module, and ``filename_generator`` is a regular
python function. Here's the skeleton for that function::
def filename_generator(file_parts, new_m_time):
return ''.join([file_parts[0], '.%s' % new_m_time, file_parts[1]])
Advanced configuration with DJANGO_STATIC_COMBINE_FILENAMES_GENERATOR
---------------------------------------------------------------------
By default, django-static generates filenames for your combined files
by concatenating the file names. You can also use your own filename
generating function by setting it in settings, like so::
DJANGO_STATIC_COMBINE_FILENAMES_GENERATOR = 'myapp.combine_filenames'
This is expected to be the equivalent of this import statement::
from myapp import combine_filenames
Where ``myapp`` is a python module, and ``combine_filenames`` is a regular
python function. Here's the skeleton for that function::
path = None
names = []
extension = None
timestamps = []
for filename in filenames:
name = os.path.basename(filename)
if not extension:
extension = os.path.splitext(name)[1]
elif os.path.splitext(name)[1] != extension:
raise ValueError("Can't combine multiple file extensions")
for each in re.finditer('\.\d{10}\.', name):
timestamps.append(int(each.group().replace('.','')))
name = name.replace(each.group(), '.')
name = os.path.splitext(name)[0]
names.append(name)
if path is None:
path = os.path.dirname(filename)
else:
if len(os.path.dirname(filename)) < len(path):
path = os.path.dirname(filename)
new_filename = '_'.join(names)
if timestamps:
new_filename += ".%s" % max(timestamps)
new_filename = new_filename[:max_length]
new_filename += extension
return os.path.join(path, new_filename)
Compression Filters
-------------------
Default (cssmin)
~~~~~~~~~~~~~~~~
django-static uses cssmin by default if it is installed.
Get the source here: https://github.com/zacharyvoase/cssmin
Using jsmin
~~~~~~~~~~~
If you would like to use jsmin instead of default js_slimmer, you just need to set
the variable in your settings.py file::
DJANGO_STATIC_JSMIN = True
Using Google Closure Compiler
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you want to use the `Google Closure
Compiler <https://code.google.com/closure/compiler/>`__ to optimize your
Javascript files you first have to download the compiler.jar file and
make sure your systam can run java. Suppose you download it in
/usr/local/bin, the set this variable in your settings.py file::
DJANGO_STATIC_CLOSURE_COMPILER = '/usr/local/bin/compiler.jar'
If for some reason the compiler chokes on your Javascript it won't
halt the serving of the file but it won't be whitespace optimized and
the error will be inserted into the resulting Javascript file as a big
comment block.
Using the YUI Compressor
~~~~~~~~~~~~~~~~~~~~~~~~
The `YUI Compressor <https://developer.yahoo.com/yui/compressor/>`__ is
both a Javascript and CSS compressor which requires a java runtime.
Just like the Google Closure Compiler, you need to download the jar
file and then set something like this in your settings.py::
DJANGO_STATIC_YUI_COMPRESSOR = '/path/to/yuicompressor-2.4.2.jar'
If you configure the Google Closure Compiler **and** YUI Compressor,
the Google Closure Compiler will be first choice for Javascript
compression.
Using the slimmer
~~~~~~~~~~~~~~~~~
`slimmer <https://pypi.python.org/pypi/slimmer/>`__ is an all python
package that is capable of whitespace optimizing CSS, HTML, XHTML and
Javascript. It's faster than the YUI Compressor and Google Closure but
that speed difference is due to the start-stop time of bridging the
Java files.
How to hook this up with nginx
------------------------------
Read `this blog entry on
peterbe.com <https://www.peterbe.com/plog/serve-your-static-stuff-in-django-with-nginx>`__
نحوه نصب
نصب پکیج whl django-static-1.5.6:
pip install django-static-1.5.6.whl
نصب پکیج tar.gz django-static-1.5.6:
pip install django-static-1.5.6.tar.gz