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
Try checking the option "Enable direct integration with GeoServer WMS" under Tile Caching, Caching Defaults for the very first time.
Under Layers select a layer and Check "Create a cached layer for this layer" under Tile Caching tab for the particular layer
Try to access the layer using the WMS endpoint from the browser
Check for a folder with the name similar to the layer name under cache directory/persistent volume mount in any of the pod where the cache volume is mounted (It might have not created)
Try deleting the WMS pod which automatically creates a new pod with the updated configurations.
Try to access the layer again and now you will notice a new folder gets created and the layers start to cache the tiles.
Possible Reason: The WMS spring microservice loads the configuration when it initially starts and not being refreshed for every configuration changes until it restarts or starts again.
Steps to reproduce:
Possible Reason: The WMS spring microservice loads the configuration when it initially starts and not being refreshed for every configuration changes until it restarts or starts again.
--
Originally reported at camptocamp/helm-geoserver-cloud#171
The text was updated successfully, but these errors were encountered: