Skip to content
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

Storage Quota Support #5227

Open
1 task done
pmazaitis opened this issue Sep 28, 2024 · 0 comments
Open
1 task done

Storage Quota Support #5227

pmazaitis opened this issue Sep 28, 2024 · 0 comments

Comments

@pmazaitis
Copy link

Describe the feature you'd like

I'd like to be able to set storage quotas on the book level. For example: a given book can only have 100MB of content in it (text + images + attachments).

Describe the benefits this would bring to existing BookStack users

Given an organization, the use case I'd like to support is:

  1. Set up a shelf for member books.
  2. Offer each member of the organization their own book that they can use to collect notes, drafts, etc.

My hope is that members would also find this a handy and low-overhead way to communicate ideas between each other (I could write something up, send someone else a link, they could easily comment, etc.).

My worry is that a member book could be used for storing large amounts of files ("Hey, I can store my music collection here and get access to it anywhere!"). Storage quotas would help.

Can the goal of this request already be achieved via other means?

I don't think so. I don't think filesystem-level quotas will help here. Implementing a community storage policy is an option, but asking nicely doesn't always work (and a filesystem filling up is usually a bad day).

Have you searched for an existing open/closed issue?

  • I have searched for existing issues and none cover my fundamental request

How long have you been using BookStack?

Under 3 months

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant