> 1. Ability to specify a common, "header", part for the base directories.
> All my users' file space is held under a "header" directory of the
> form "/path/to/user/file/space". At the moment, for each user's base
> directories, I have to specify a base directory path that includes the
> "header" details. I'd like to be able to put just the user's
> distinctive file directory in file_manager.users. i.e. have
> "/users/filedir" rather than "/path/to/user/file/space/users/filedir"
Easy. I'll put it on my short list.
> 2. Ability to specify a display name for each base directory.
> At the moment a base directory of
> "/path/to/user/file/space/users/filedir" will have a display name of
> "filedir". I'd like to be able to specify a display name of say
> "Web1"; possibly, in combination with 1 above, using a syntax of
I don't really understand that syntax, but moreover, there will be 100
other people who want a different syntax. A string substitution kind of
thing might be better, but this will take some more thought. Since
there can be any number of base directories, this also creates the need
for something like an associative list of base dir paths that map to a
"displayable name"... I'm not sure what you gain from showing the
parent directory to the user's base directory, however, and I am
hesitant to add that for security reasons.
> 3. Ability to share a common quota over a user's combined file space.
> Currently a specified quota (e.g. 10M) will be applied to each base
> directory separately (each base getting its own 10M quota). It would
> be nice if, as an option, the quota could be specified as being the
> total allowed for all base directories together (the total file space
> used summed across all bases must not exceed 10M).
This is a little more work, but I'll add it to my list.
> 4 Ability to use a MySQL table instead of the file file_manager.users
And yet more work... not hard, but more work. This one goes on my long
list unless someone else wants to do it.
Thanks for the ideas,