Where to Configure Cache Storage in Evolution CMS

One of the most common admin questions is where cache storage is configured. The manager gives you a way to clear cache, but the cache backend itself is configured in the application layer.

Where the setting lives

In an Evolution CMS project, cache storage is typically configured in the cache config file:

/core/config/cache.php

Depending on the project, you may see supported drivers such as:

'file', 'array', 'database', 'redis', 'memcached', 'apc'

Which driver should you use?

• file is the safest default for most small and medium projects
• redis is strong for larger projects or multiple app nodes
• memcached can also work well in distributed setups
• array is useful mainly for testing and per-request memory use
• database is possible, but usually not the first choice for performance

Recommended default

If you are not running a dedicated caching service yet, use file cache first. It is easy to understand, easy to clear, and stable on most hosting environments.

When to move beyond file cache

• high traffic and repeated expensive queries
• multiple web nodes that need shared cache state
• projects already using Redis for queues or sessions

The important point is that clearing cache in the manager and choosing the cache backend are two different tasks. The first is routine maintenance. The second is environment configuration.