Arthur Bodera

Meh, this just hit me in the face. The way I usually work with asset collections (see assetic and node.js stuff) is that collections _might_ be accessible in debug mode...

I see the problem in architecture... collection resolver is an aggregate, so it is able to use other resolvers for stackability. That's actually quite cool, but is source of the...

Another idea is separation of production and devel by moving out "compilation" (merging, filtering) outside of the standard asset serving. The standard workflow (for most websites) is: 1. **devel** :...

@RWOverdijk you're missing my point mate. Acl is a terrible idea... Compilation is part of the asset management. Why would you use jsmin filter with AssetManager in development ? The...

> Additional note: please stay on topic and forget about the compilation part. Let's move that to another issue eventually. Additional note: I am on topic :-) > That is...

> And no, you're not on-topic. The topic is "how do we hide files from some resolvers?" Yes I am. If the compilation/warmup worked as expected, we wouldn't have access...

sigh :sleepy: If it was feasible and fulfilled the requirements I've stated 2 screens above, there wouldn't be any discussion.

> AssetManager works as a cache, and as a MVC fallback on 404s. Then call it a `AssetCache*` (the asterisk is there so you can explain in detail why exactly...

Confirmed. I have determined that storage is unreadable since 913897f424af319a0fa67d5356454de1512efeae up. Previously my files were compressed with fusecompress 9d5137d7d067151a9822b40e3687b0f645b33937 with method `-o fc_c:lzo` and `libboost-serialization.1.44`, but after installing new version...

Also see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629874