Andy McKay wrote:
Oliver Bleutgen wrote:
I'm looking for a product which allows me to manage files in zope which reside on the filesystem, and provide a natural way to be served from apache. As far as I see, none of LocalFS, ExternalFile, ExtFile provide a way to do that naturally - for instance by providing the 'precondition' property (to raise an appropriate redirect) or to allow an definable <a href="<something"> string to be rendered when called, analogous to the Image object.
Im not sure what you mean, LocalFS is all about managing FS things from Zope.
Perhaps you might mean something like FS Cache Manager which takes objects served from and puts them on the File System in cache to be served from the FS using Apache, and works great for File and Image objects. http://www.zope.org/Members/andym/FSCacheManager
Thanks for the answer, and sorry for not being clearer, but I not quite sure myself how to really accomplish what I want. What I need is: 1) Files shouldn't be stored in the zodb 2) Files should be managable (delete, create, update) from zope 3) Files shouldn't be served from zope 4) No additional administration outside apache is needed. The products I mentioned accomplish 1), 2) and 4). They can accomplish 3), but only if users always remember to link to these files in a "special" way, i.e. with a different path than they would link them if they were normal zope objects. FS Cache Manager accomplishes 3) (at least well enough for me), but not 4), while I wouldn't mind 2 lines in httpd.conf. That's why I thought about a product like LocalsFS which would just - instead of delivering the file when it's called from the web - raise a redirect to an appropriate URI where then apache would serve the file. cheers, oliver