Self-host Redis Commander with Levelrail

A web interface to browse and edit Redis keys. It comes with its own Redis service, and both the Redis password and the web login password are generated for you and shown in the deployment variables.

  • Authorjoeferner
  • LicenceMIT
  • Memory128 MiB
  • Services2

How to self-host Redis Commander

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • redis:7.4.7-alpine
    • ghcr.io/joeferner/redis-commander:0.9.0
  2. Create the app

    2 services start in a single Compose app, with 1 named volume mount for your data, on port 8081.

  3. Fill in the secrets

    3 secrets are generated and stored encrypted, 1 setting is preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Sign in as admin with the generated password. To browse another Redis, change REDIS_HOSTS in the deployment settings.

Redis Commander requirements

Memory
About 128 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
8081
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Redis Commander. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Redis Commander docs page.

Deploy Redis Commander your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Redis Commander from the CLI

levelrail-cli templates deploy redis-commander --name my-redis-commander

Deploy Redis Commander with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/redis-commander/deploy

Redis Commander configuration

Redis Commander services

ServiceImagePortsVolumes
redis redis:7.4.7-alpine none redis_data -> /data
redis-commander ghcr.io/joeferner/redis-commander:0.9.0 8081 none

Redis Commander environment variables

VariableServiceValue
REDISCLI_AUTH redis Generated at deploy
HTTP_PASSWORD redis-commander Generated at deploy
HTTP_USER redis-commander Preset by the template
REDIS_HOSTS redis-commander Generated at deploy

Ports and volumes

Ports
8081
Volumes
1 named mount: redis_data -> /data

Redis Commander FAQ

How much memory does Redis Commander need?

The catalog lists about 128 MiB of memory for Redis Commander across its 2 services.

Does Redis Commander run on arm64?

For Redis Commander, arm64 support is not confirmed; amd64 is unknown.

What licence is Redis Commander under?

Redis Commander is licensed under MIT, which is permissive, with few conditions on reuse.

Does Redis Commander need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does Redis Commander bundle?

The template includes Redis, running as its own service.

Which ports does Redis Commander use?

Redis Commander listens on port 8081 inside the stack.

Where does Redis Commander keep its data?

In a named volume: redis_data mounted at /data.

Can I deploy Redis Commander on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Redis Commander, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image redis:7.4.7-alpine, ghcr.io/joeferner/redis-commander:0.9.0 is what you deploy there.

levelrail-cli templates deploy redis-commander --name my-redis-commander