Skip to content
Browse files

updated the readme to current state

  • Loading branch information...
1 parent 3b5d09b commit 45f1236ef8cf155f4dc8c3f7ccaad95581043527 michael committed Jun 12, 2008
Showing with 12 additions and 4 deletions.
  1. +12 −4 README
@@ -78,6 +78,11 @@ via the filesystem modification dates. Currently, the only other usuable
values are "always" and "never", the former only recommended during debugging,
the latter useful if you want to limit yourself to manual building.
+ASSETS_AUTO_CREATE defaults to True and can be used to disable automatic
+creation of an assets even if it does not exist yet. This is useful in
+combination with ASSETS_UPDATER="never", to disable any sort of automatic
+asset building.
ASSETS_EXPIRE is needed if you send your assets to the client using a far
future expires header. Unless set to False, it will modify the asset url
using it's modification timestamp, so that browsers will reload the file
@@ -106,8 +111,11 @@ Future TODOs
image urls with timestamps; the cssrewrite filter could modify urls within
CSS files when ASSETS_EXPIRE is enabled.
+ * Find a good solution to making filter debug/log information available in a
+ standardized way across the board.
- * Nodes in child templates are always not correctly found by rebuild command?
- * Add autocreate option to disable automatic creation even if not exists (
- source files are outputted instead)
+ * Allow an option to fall back to rendering source files in case asset
+ building fails for some reason. Right now, the user would get to see a
+ server error. This would probably most simply be accomplished by having
+ AssetsNode catch exceptions in create_merged() and redirect to
+ render_sources. We probably want to activate this only in production mode.

0 comments on commit 45f1236

Please sign in to comment.
Something went wrong with that request. Please try again.