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

Enhancement: cache management - flush, inspect, remove individually #4

Open
robbieaverill opened this issue Jan 2, 2017 · 2 comments
Milestone

Comments

@robbieaverill
Copy link
Contributor

robbieaverill commented Jan 2, 2017

  • cache:list: list all cache IDs as well as some information about them
  • cache:dump: Dump the contents of everything in the cache, or by ID
  • cache:flush: Clear the entire cache manifest
  • cache:view: View the contents of specific cache entries by key This can be incorporated as an argument of cache:dump
  • cache:remove Remove specific cache entries by key

I'm not sure that the ConfigManifest will actually let us do these:

  • cache:enable: Enable the global cache (if disabled)
  • cache:disable: Disable the global cache (if enabled)
@robbieaverill
Copy link
Contributor Author

I've rejigged the requirements for this after an initial investigation. I don't think enable and disable would be doable with the way the manifest is loaded on every request.

@robbieaverill robbieaverill modified the milestones: 1.0.0, 1.1.0 Jan 25, 2018
@robbieaverill robbieaverill removed their assignment Jan 25, 2018
@robbieaverill
Copy link
Contributor Author

SilverStripe's cache management is still fairly singular. You can configure different cache services via injector, which is something that we could surface with a command like this (e.g. cache:list lists all CacheInterface implementations registered under Injector, with their cache status, TTL etc), and we could allow each of them to be individually flushed.

I expect in future that more granular cache entry separation and handling might become more important in core, so this could be a useful command to add proactively.

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

2 participants