Portabase AgentDatabases
Valkey
Configuration for Valkey.
The agent will use valkey-cli to perform backups.
Configuration with Auth
{
"name": "Valkey Database Auth",
"type": "valkey",
"host": "db-valkey-auth",
"port": 6379,
"username": "username",
"password": "password",
"generated_id": "..."
}Configuration without Authentication
{
"name": "Valkey Database",
"type": "valkey",
"host": "db-valkey",
"port": 6379,
"generated_id": "..."
}Docker Compose Example
services:
db-valkey:
image: valkey/valkey
container_name: db-valkey
environment:
- ALLOW_EMPTY_PASSWORD=yes
ports:
- '6381:6379'
volumes:
- valkey-data:/data
networks:
- portabase
db-valkey-auth:
image: valkey/valkey
container_name: db-valkey-auth
command: >
--requirepass "supersecurepassword"
ports:
- '6382:6379'
volumes:
- valkey-data-auth:/data
networks:
- portabase
agent:
image: portabase/agent:latest
# ... agent configuration ...
networks:
- portabase
networks:
portabase:
external: true
volumes:
valkey-data-auth:
valkey-data:Important: Localhost and Docker
If you use localhost as the host (because the agent is on the host machine and not in Docker, or via host-gateway), ensure your database is listening on all interfaces (0.0.0.0) or is accessible from the agent.
Try this: "host": "host.docker.internal" (replace host in config.json, toml) or "host": "db-valkey" (if using Docker Compose).
Last updated on