Skip to content

Redis

Applications may use Redis for caching, sessions or queues. Restart impact and data protection depend on its use and configuration.

Available versions

The redis-server package version from the server repositories. The current catalog has no separate Redis branch selector. The exact release depends on the system and available packages.

These options come from the application installation catalog. A catalog entry alone does not guarantee package availability on every server; verify the exact installed version in the service inventory.

Install

  1. Choose Redis in services or a profile that includes it.
  2. Refresh the inventory and verify service state after completion.
  3. Configure application connectivity and test it from that environment.

Configure

The editor exposes /etc/redis/redis.conf. Check listening address, port, authentication and persistence according to application requirements. An available service does not mean the application's cache is configured correctly.

Set address and credentials in the project environment or application configuration. For multiple applications, plan data separation using options supported by the client and server.

Queues and processes

If Redis is a queue backend, a processing worker must also run. Installing Redis alone starts no worker.

Restart and uninstall

Assess user sessions and pending jobs before restarting. Do not assume every value survives a restart. Before uninstalling, check all dependent projects and preserve required data.