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

Settings Engine Expiration Policy For History Should Be Configurable #4747

Open
wixbot opened this issue Apr 27, 2015 · 1 comment
Open

Settings Engine Expiration Policy For History Should Be Configurable #4747

wixbot opened this issue Apr 27, 2015 · 1 comment
Assignees
Milestone

Comments

@wixbot
Copy link

wixbot commented Apr 27, 2015

Right now the policy is probably good as a default for most users, but cannot be customized. Users should be able to control how much history they want to keep or discard.

This should be customizable differently for different machines (per-machine setting), and also configurable on individual remote databases, as certain ones will be more storage constrained than others.

It might also be interesting to offer a quota setting that limits storage to a specific amount - for example, a user might want to devote only 1 GB of their dropbox account to settings history, but more on their NAS.

Originally opened by mike-gc

@wixbot
Copy link
Author

wixbot commented Sep 3, 2015

Originally changed by mike-gc
AssignedTo set to mikegc

@wixbot wixbot added this to the v4.x milestone Dec 20, 2015
@rseanhall rseanhall modified the milestones: v4.x, Settings Feb 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants