/usr/share/doc/python-webassets-doc/html/_sources/faq.txt is in python-webassets-doc 3:0.9-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 | .. _faq:
FAQ
---
Is there a cache-busting feature?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Yes! See :doc:`/expiring`.
Relative URLs in my CSS code break if the merged asset is written to a different location than the source files. How do I fix this?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Use the builtin :ref:`cssrewrite <filters-cssrewrite>` filter which
will transparently fix ``url()`` instructions in CSS files on the fly.
I am using a CSS compiler and I need its filter to apply even in debug mode!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
See :doc:`css_compilers` for how this is best done.
Is Google App Engine supported?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Yes. Due to the way Google App Engine works (static files are stored on
separate servers), you need to build your assets locally, possibly using one
of the management commands provided for your preferred framework, and then
deploy them.
In production mode, you need to disable the ``Environment.auto_build`` setting.
For URL expiry functionality, you need to use a manifest that holds version
information. See :doc:`/expiring`.
There is a barebone Google App Engine example in the
`examples/appengine/ <https://github.com/miracle2k/webassets/blob/master/tests/>`_
folder.
|