Man, I'm torn on this one - having the repsitory objects in the db as blobs sounds like a neat option, and I can think of applications immediately.  But I need to keep a leash on my customer's data footprint, and having the files on the disk where I can see them lets me know how they're doing.  The files they upload are going to be the big ticket on their storage needs.  I plan on using the size restrictions and doing some education on how to use a logo properly but ...

So I guess there are real pros and cons, so in the long term, is there hope of making this optional, or will that make the code too crazy?

Hi,

first of all I would like to thank you for your great work. I really like this module.

I would like to propose a small enhancement for the repository dashboard causing a big effect.
By adding an (optional) category filter in the dashboard's module settings, we would be able to set up flexible security settings within one repository module. Imagine a repository with several categories and two or more dashboards. Each of the dashboards is viewable for different usergroups and points to different categories. Adding files to the repository, you could then neatly select who can download this file by assigning the appropriate categories.

Ideally the category filter should be a multiselectbox.

Regards,
Marcel