valkey
| Version | 2026.144.1443 |
| Repo | superproject |
A Redis-compatible Valkey 9.x key-value server (valkey-server + valkey-cli) supervised on 0.0.0.0:6379
Installs Valkey 9.x from the Remi modular repo (the valkey
package, module valkey:remi-9.0), which ships /usr/bin/valkey-server
and /usr/bin/valkey-cli. A supervised valkey-server binds
0.0.0.0:6379 with protected-mode off, a ${HOME}/.valkey data dir,
and a 60s/1-key RDB snapshot policy, so the running service answers
valkey-cli ping with PONG, stores and returns key-value pairs, and
accepts TCP on its published host port. Every claim below is
verifiable: the binaries on disk, the valkey package installed,
and a live PING/PONG + SET/GET round-trip + reachable-port probe
against the running deployment.
Services
Section titled “Services”valkey
Acceptance plan
Section titled “Acceptance plan”This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.
| Intent | Step |
|---|---|
run |
mkdir=${HOME}/.valkey |
check |
the valkey-server daemon binary is installed at /usr/bin/valkey-server |
check |
the valkey-cli client binary is installed at /usr/bin/valkey-cli |
check |
the valkey package is installed |
check |
valkey-cli ping returns PONG against the supervised valkey-server |
check |
the valkey port accepts a TCP connection from the host |
check |
a value written with SET can be read back with GET, proving the store really persists key-value pairs |
agent-check |
the supervised valkey service is running and keeps answering clients, restarting automatically (restart=always) if the valkey-server process exits |
check |
command=valkey-cli -h 127.0.0.1 -p 6379 ping |
check |
command=valkey-cli -h 127.0.0.1 -p 6379 set charly-check-probe charly-check-ok && valkey-cli -h 127.0.0.1 -p 6379 get charly-check-probe |