Skip to main content
Open console

Redis

In-memory cache

1 min read

In-memory cache, for what expects Redis by name. Valkey is the fork most stacks now take: an application written against one runs unchanged on the other.

A stack runs one cache: Redis, Valkey or Memcached. Naming a different one replaces it.

Your application finds it at REDIS_HOST, port 6379 (REDIS_PORT). Both are in its environment, and REDIS_HOST is the name the Drupal redis module reads.

Its memory is sized from your machine: most of a cache machine when it has one to itself, a share of your plan when it sits beside your site. When it is full it evicts the least recently used key (allkeys-lru).

Keeping its data

REDIS_PERSISTENCE says what Redis keeps on disk:

Value Keeps
off (the default) Nothing: a restart empties it
snapshots A snapshot every few minutes; a restart comes back warm
store Every write, and nothing evicted: noeviction, whatever REDIS_MAXMEMORY_POLICY says

Set it in vallic.yaml or for one environment under Service settings. It works as Valkey's does: on the machine's own disk, and in the nightly backup as a store.

From your own computer, vallic tunnel <env> redis opens it on 127.0.0.1:6379 for a desktop client or a browser. See Tunnels.

Versions

Version Status
8.6 Supported, and the default
8.10 Supported
8.4 Supported
8.2 Supported

Pin the version, not the build: name 8.6 and the platform matches it to the current build, so a security rebuild reaches you without anybody editing a repository.

What you can change

In vallic.yaml — what each one does is on Service settings:

services:
  - redis:
      version: '8.6'
      environment:
        REDIS_MAXMEMORY_POLICY: …
        REDIS_DATABASES: …
        REDIS_PERSISTENCE: …

Anything not on this list refuses the deploy, naming the variable — rather than being accepted and quietly ignored.

Need a hand?

Open a ticket from Support in the console. We answer on the ticket.

Open the console How support works