Global config with updated_at timestamp #8072
Unanswered
BrandonOldenhof
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
I'm trying to improve our site performance by implementing some caching.
We're doing some calls to the global config in our templates so I'm trying to cache those calls. The best way, I think, would be to set a dynamic cache key based on an automatically-updated
updated_at
field, but I noticed my globals don't have that functionality.I already found some documentation that points me in the direction of Computed Values. So my idea would be to manually add a
updated_at
date field to the global's blueprint and automatically update it using the Computed Values functionality, but I'm not sure if that would be the best way to go about it; it feels like overkill.What would be the best way to get an automatically-updating
updated_at
value from my Globals so I can use it as part of a cache key?Beta Was this translation helpful? Give feedback.
All reactions