Managing caching on Kelma

Kelma caches your site at several layers so most requests are answered in single-digit milliseconds — and it is all tuned for you. You rarely need to touch it, but the panel gives you simple controls for the times you do, like clearing the cache after a deploy or temporarily bypassing it while you debug.

The caching layers

• Cloudflare full-page caching — serves cached HTML to anonymous visitors straight from the edge nearest them. Logged-in users always bypass it, so wp-admin and carts stay correct.
• Nginx FastCGI cache — a server-side page cache that speeds up PHP/WordPress responses for requests that do reach the origin.
• Redis object cache — caches database queries and objects in memory, managed automatically.

Clearing the cache

Caches purge automatically when content changes, so you usually do not need to do anything. When you do want to force a clear — after a manual file change, say — use:

• Clear CF cache in the site sidebar — purges the Cloudflare edge cache.
• Flush FastCGI cache on the caching settings — clears the server-side page cache.

Development mode

Debugging something and need to see changes instantly? Turn on Development mode to bypass the Cloudflare cache for 30 minutes. It switches itself back off automatically, so you cannot forget and leave caching disabled.

Tips & tricks

• Seeing a stale page? Clear the CF cache first, then the FastCGI cache — that covers both layers.
• Building a theme? Flip on development mode so every refresh shows your latest CSS/JS without a hard-refresh dance.
• Carts or logged-in pages acting cached? They should not be — those bypass caching automatically. If you see issues, reach support; do not disable caching site-wide.
• After a deploy, a quick CF purge guarantees visitors get the new version immediately.

Where to go next