You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These hard coded values are not suitable for many use cases where the website has many pages and needs more than 512Mb of cache size, or the website has a low visitors count and pages are not accessed in a 30 minutes timeframe twice but still needs cache because of high page generation time.
I suggest allowing user to set these values along with fastcgi_cache_valid duration, which is already configurable in web domain UI.
Would you like to sponsor this feature to have it implemented?
No
The text was updated successfully, but these errors were encountered:
Describe the feature or change in detail
Currently hestia cp uses 512Mb max size and 30 minutes inactive time for nginx fastcgi cache:
hestiacp/bin/v-add-fastcgi-cache
Line 83 in 2f4b15a
These hard coded values are not suitable for many use cases where the website has many pages and needs more than 512Mb of cache size, or the website has a low visitors count and pages are not accessed in a 30 minutes timeframe twice but still needs cache because of high page generation time.
I suggest allowing user to set these values along with
fastcgi_cache_valid
duration, which is already configurable in web domain UI.Would you like to sponsor this feature to have it implemented?
No
The text was updated successfully, but these errors were encountered: