-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Directory-based quota #1763
Comments
Discussed here: https://twitter.com/patschi95/status/786685701542797312 |
Could you share a usecase, Patschi, what is the problem you are trying to solve with this? |
It offers in combination with the already-existing and awesome features like External storage and File Access Control many new possibilities - some examples:
The first usecase is mainly the reason behind this feature request. By default Nextcloud is not counting the used space of external storages upon the users´ quota, but beside that it may even be possible that the external storage have a server-side quota itself but Nextcloud is not aware about that. So by implementing such a feature like directory-based quota it may be possible to use that functionality to make Nextcloud aware of that quota while offering the users even more flexibility to set custom quota on their own (shared) folders. This allows to prevent any misbehaviour/errors when trying to put files onto a external storage where the server-side quota is already exceeded. |
This comment was marked as duplicate.
This comment was marked as duplicate.
I guess the only 'news' is that as far as I can tell nobody is working on it (yet) ;-) |
If this feature is triaged enough now, shouldn't be the label "1. to develop" assigned to it? |
Same news as in December ... Nobody is working on it (yet). Changing the label will not change the state of development ... It is currently in triage, because none of the developers has yet thought over an implementation - or closer details :( |
Oh, sorry! Then I understood the label "to triage" a bit wrong :) I thought it means, that it's still being considered if the dev team wants the feature within Nextcloud. (I interpreted "1. to develop"-label like "Feature request valid, anyone can start developing it now"-label :P) |
My use case (NC12.0.0): An external WebDAV Folder is shared with a user group. I cannot set a per group quota and i cannot set a per folder quota, so every user can upload as much as he/she wants. The result is a completely filled WebDAV storage. Such a feature would be very welcome. It seems to have been recently implemented in "groupfolders" app: |
The Group folders app lets you set a total max quota on each folder and yeah, it would be possible I suppose to add a total quota to external storage, too. It would at least cover some of the needs for this. But besides that, it is a complicated thing from what I can tell - both on how to define proper behavior (should you allow a user to exceed their quota? how does it count? Can users set a quota for others whom they share folders with? etc) and in terms of how to implement. It would probably require a serious amount of time and work, meaning it isn't likely somebody does it in their free time. Which would mean it probably requires a customer request to Nextcloud GmbH or a company to pay a third party to do it and get it upstream. I might be wrong, though - just sharing my thoughts to create realistic expectations 😸 |
Would be nice to see this. In our setup, user has only small quota. Users are expected to add external SMB storage with 1 TB available for each user. While the used space is correctly (afaict), users don't see how much space they've got left. |
The existing (but not well known I suspect) https://github.com/nextcloud/groupquota In addition to, of course, the quota support that already exists in the |
Expected behaviour
A great new feature would be a directory-based quota. Which can be within the total quota limit, or can even be overwritten by any specific quota (even more than the total quota).
Actual behaviour
Only setting one total quota is possible.
The text was updated successfully, but these errors were encountered: