Add note about config cache expiration setting
This commit is contained in:
parent
c7f585dfed
commit
945320d1eb
|
@ -114,6 +114,21 @@ the paths if you prefer::
|
||||||
beaker_cache.data_dir = /somewhere/else/data
|
beaker_cache.data_dir = /somewhere/else/data
|
||||||
beaker_cache.lock_dir = /somewhere/else/lock
|
beaker_cache.lock_dir = /somewhere/else/lock
|
||||||
|
|
||||||
|
Note that by default there is *no expiration* for the cache values,
|
||||||
|
meaning once a particular setting is cached, that value will never
|
||||||
|
expire, and therefore the setting will never be re-fetched from DB
|
||||||
|
(unless a new value is written for it, in which case the cache is
|
||||||
|
invalidated for that setting, which causes a re-fetch next time it's
|
||||||
|
requested). You may want values to expire after say, an hour, so that
|
||||||
|
settings will periodically be re-fetched regardless of write activity.
|
||||||
|
Do that by specifying the number of seconds after which values should
|
||||||
|
expire::
|
||||||
|
|
||||||
|
[rattail.config]
|
||||||
|
# nb. expire values after 1 hour
|
||||||
|
beaker_cache.expire = 3600
|
||||||
|
|
||||||
|
|
||||||
memcached
|
memcached
|
||||||
=========
|
=========
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue