Skip to content
SuperDOCS

Deployment

SQLite deployment

Section titled “SQLite deployment”
Terminal window
docker compose -f docker/compose.sqlite.yml up --build

PostgreSQL deployment

Section titled “PostgreSQL deployment”
Terminal window
docker compose -f docker/compose.postgres.yml up --build

Production environments need durable system storage and a securely injected application secret. SQLite deployments should regularly test encrypted backup and restore.

Reverse-proxy prefix

Section titled “Reverse-proxy prefix”

Relative production assets and API URLs let one image run below /platform/tools/redis/:

location /platform/tools/redis/api/ {
    proxy_pass http://super-redis-manager:4051/api/;
    proxy_cookie_path / /platform/tools/redis/;
}
location /platform/tools/redis/ {
    proxy_pass http://super-redis-manager:4050/;
}

Use the Compose files as the authority for production internal port mappings. Keep trailing slashes on proxy_pass and do not set a fixed VITE_PUBLIC_BASE.

Production checklist

Section titled “Production checklist”
  • Use HTTPS and controlled network ingress.
  • Set a stable SUPER_REDIS_MANAGER_SECRET_KEY.
  • Back up and restore-test the system database.
  • Restrict target Redis networks.
  • Store SSH keys, Redis passwords, and database credentials in a secret manager.
  • Tune proxy timeouts and request limits for real usage.