Skip to content

Flint Engine — The eCommerce Operating System

Flint Engine eCommerce OS
Live Demo Get Started

Cache

September 18, 2026 v1.0

Overview

Flint Engine uses caching to improve performance by storing frequently accessed data in memory. Cache is managed automatically behind the scenes — settings changes trigger cache clearing automatically.

How Caching Works

Flint Engine uses a file-based or Redis-based cache depending on your server configuration. The cache stores:

  • Site settings and configuration
  • SEO settings and metadata
  • Database query results
  • Template fragments

Automatic Cache Clearing

Cache is cleared automatically when you make changes through the admin panel:

  • Settings changes — When you save settings in Settings, the settings cache is cleared
  • SEO changes — When you update SEO settings, the SEO cache is cleared
  • Content updates — When you publish or modify content, relevant caches are refreshed

Clearing Cache Manually

If changes do not appear immediately on your site, you can clear the cache through the command line:

# Clear all cached data
php artisan cache:clear

# Clear configuration cache
php artisan config:clear

# Clear route cache
php artisan route:clear

# Rebuild optimized files
php artisan optimize

Cache Types

Cache Type What It Stores When It Clears
Settings Cache Site configuration values When settings are saved
SEO Cache SEO metadata and settings When SEO settings are updated
Data Cache Database query results When related content changes

Redis Configuration

For production environments, Redis is recommended for better performance:

  • Set CACHE_DRIVER=redis in your .env file
  • Configure REDIS_HOST, REDIS_PORT, and REDIS_PASSWORD
  • Redis provides faster cache reads and supports distributed caching

Tip: In most cases, you do not need to manually clear the cache. Settings changes trigger automatic cache clearing. Only use manual cache clearing if you notice stale content after changes.

Troubleshooting

  • Changes not appearing — Clear the cache via command line or wait a few minutes
  • Stale content — The cache may not have cleared automatically; run php artisan cache:clear
  • Performance issues — Ensure Redis is configured correctly if using Redis caching