1.4.5.5.6. Configuration 1.4.5.5.6.2. "Cache Configuration" tabbed page |  |
| Prev | Next |
User groups have separate caches for $CADENAS_DATA [User groups have separate caches for $CADENAS_DATA]:
Enabled: If you want security, then you can't use preloading; you can only cache on demand, that is, little by little with each incoming request. The request is placed in the cache for the respective user group, and the next user from the same user group receives the data.
Disabled: If you're willing to accept a little uncertainty (since there is no distinction between user groups ), you can preload all data in the background. This way, you don't have to wait even on the first load.
At the specified interval, the system checks whether the configured catalogs are fully present in the local cache.
Background refresh for $CADENAS_DATA [Background update for $CADENAS_DATA]: Based on the configured time, the system checks whether everything has been preloaded into the local cache.
Only the following directories [Only the following catalogs]: Option to restrict access to specific directories. (This would allow you to omit user differentiation, but only for specific directories.)
Storage location for the RFS cache: Enter via browser or direct entry (if administration takes place on the app server and you do not have direct access to the cache server at all). For example, $CADENAS_USER/rfs2
Maximum cache size: Limits the amount of storage space, in gigabytes, that the cache may occupy at the specified location (default: 10 GB). If this limit is exceeded, the oldest entries are removed.