{% extends "baseTemplate/index.html" %} {% load static %} {% comment %} /cache/objectCache — Redis (or an operator-run Memcached) for one website. The credentials shown here belong to the site being looked at and to nobody else: the panel creates a Redis ACL user per site whose key pattern is that site's prefix, so the password below unlocks exactly this site's keys. {% endcomment %} {% block title %}Object cache{% endblock %} {% block styles %} {% include "cacheManager/_styles.html" %} {% endblock %} {% block content %}
Redis in front of your application's database queries and computed values.
Every website on this server shares one Redis instance, so CloudPanel confines each site to its own key namespace and creates a Redis user whose key pattern is exactly that namespace. A request for a key outside it is refused by Redis itself, not by a convention in a configuration file.
For a WordPress site these are already written into wp-config.php. For anything else, point your application's cache client at them. The password is not shown again here — it is written into the site's own configuration file, which the site owns.
| Host | |
|---|---|
| Port | |
| Database | |
| User | |
| Key prefix |
Websites connect over loopback TCP. The unix socket is mode 0770 redis:redis and is reserved for the panel.
Enabling the object cache installs the Redis object-cache plugin, writes the connection constants into wp-config.php and copies the plugin's object-cache.php drop-in into wp-content/. Disabling removes all three.
Choose a website to see its object cache.