Jabali Cache

FAQ

The status says Redis is “Not reachable”. What do I do?

On the Jabali panel, socket access is set up when you enable caching for the site (Applications → cache toggle). If the status still shows Not reachable, re-run that toggle.

On a standalone host, the site’s PHP-FPM user needs two things for a unix socket:

1. open_basedir must allow the socket’s directory — add /run/redis (or wherever your socket lives) to the pool’s open_basedir.
2. Read/write access to the socket for the PHP-FPM user.

Until that is in place the plugin runs as a normal per-request cache and the site is completely unaffected — caching just isn’t persistent yet.

Does it need the phpredis (PECL redis) extension?

No. It auto-detects phpredis and uses it when available; otherwise it uses a built-in pure-PHP client. You get persistent caching either way.

How do I use it outside the Jabali panel?

Define overrides in wp-config.php. With none of these set, it defaults to the Jabali socket and a per-site prefix.

define( 'JABALI_CACHE_SOCKET', '/path/to/redis.sock' ); — unix socket, or:
define( 'JABALI_CACHE_HOST', '127.0.0.1' );
define( 'JABALI_CACHE_PORT', 6379 );

Optional:
define( ‘JABALI_CACHE_DB’, 1 ); — logical database number
define( ‘JABALI_CACHE_PASSWORD’, ‘…’ ); — Redis AUTH password
define( ‘JABALI_CACHE_PREFIX’, ‘mysite’ ); — key prefix (auto-derived per site if unset)
define( ‘JABALI_CACHE_DISABLED’, true ); — force off without deactivating

Will it isolate my cache from other sites on the same server?

Yes. Each install uses a unique key prefix, so reads, writes, and flushes are scoped to your site only. One site cannot see or clear another’s cache, even though they may share the same Redis database.

Is it safe if Redis runs out of memory?

Yes. The expected policy is allkeys-lru — Redis evicts least-recently-used keys when full. Every read in this plugin is best-effort, so an evicted key just rebuilds from the database. There is no error path that can break the site under memory pressure.

Does it work on WordPress Multisite?

Yes. Per-site cache data is namespaced per blog, while truly global cache groups are shared across the network as WordPress expects.

Should I also turn on the page cache?

Only if your host does not already have one. On Jabali, nginx serves a FastCGI microcache at the edge, which is faster than caching in PHP — so the WordPress page cache stays off by default to avoid double-caching. Off Jabali, you can enable it from the settings screen.

How do I manage it from WP-CLI?

wp jabali-cache status # connection, driver, prefix, key count, page-cache state
wp jabali-cache flush # flush this site’s object cache
wp jabali-cache flush –pages # also purge page-cache entries
wp jabali-cache enable # enable caching
wp jabali-cache disable # disable caching
wp jabali-cache update-dropins # (re)install the wp-content drop-ins
wp jabali-cache remove-dropins # remove the drop-ins
wp jabali-cache diagnose # full connectivity + environment report

What happens when I uninstall it?

Deactivating removes the object-cache.php drop-in cleanly, so WordPress reverts to its built-in non-persistent cache. Uninstalling removes the plugin’s options. Your Redis data is just a cache and is safe to discard.