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.

Sign up for GitHub

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

Jump to bottom

Allow cache namespace to be configurable #1879

Closed
acelaya opened this issue Sep 17, 2023 · 0 comments · Fixed by #1891
Closed

Allow cache namespace to be configurable #1879

acelaya opened this issue Sep 17, 2023 · 0 comments · Fixed by #1891
Labels
feature
Milestone
3.7.0

Comments

@acelaya
Copy link
Member

acelaya commented Sep 17, 2023

Summary

Right now Shlink has a hardcoded Shlink prefix for all cache keys.

Make this configurable via env var or config option.

Use case

If multiple Shlink instances are sharing the same cache storage, cache entries can conflict, which is specially problematic if they are running under different versions.

See #1862 and #1863 for more context
@acelaya acelaya added this to the 3.7.0 milestone Sep 17, 2023
@acelaya acelaya added this to Shlink Sep 17, 2023
@acelaya acelaya moved this to Todo in Shlink Sep 17, 2023
@acelaya acelaya mentioned this issue Sep 17, 2023
Closed
@acelaya acelaya moved this from Todo to In Progress in Shlink Sep 23, 2023
This was referenced Oct 6, 2023
Merged
Merged
@acelaya acelaya moved this from In Progress to In review in Shlink Oct 6, 2023
@github-project-automation github-project-automation bot moved this from In review to Done in Shlink Oct 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
Shlink
Archived in project
Milestone
3.7.0
Development

Successfully merging a pull request may close this issue.

Feature/customizable cache namespace acelaya-forks/shlink
1 participant
@acelaya