Self-host Redis Cache Starter with Levelrail

A web service backed by a Redis cache, the cache-aside pattern most apps reach for first.

  • Memory192 MiB
  • Archarm64
  • Services2

How to self-host Redis Cache Starter

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • redis:7-alpine
    • node:22-alpine
  2. Create the app

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

  3. Fill in the secrets

    2 settings are 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.

Redis Cache Starter requirements

Memory
About 192 MiB
Architectures
amd64 image published, arm64 image published
Ports
3000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
not yet recorded
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 3000 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Redis Cache Starter. 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 Cache Starter docs page.

Deploy Redis Cache Starter your way

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

Deploy Redis Cache Starter from the CLI

levelrail-cli templates deploy redis-cache-starter --name my-redis-cache-starter

Deploy Redis Cache Starter 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-cache-starter/deploy

Redis Cache Starter configuration

Redis Cache Starter services

ServiceImagePortsVolumes
cache redis:7-alpine none redis_cache_data -> /data
web node:22-alpine 3000 none

Redis Cache Starter environment variables

VariableServiceValue
NODE_ENV web Preset by the template
REDIS_URL web Preset by the template

Ports and volumes

Ports
3000
Volumes
1 named mount: redis_cache_data -> /data

Redis Cache Starter FAQ

How much memory does Redis Cache Starter need?

The catalog lists about 192 MiB of memory for Redis Cache Starter across its 2 services.

Does Redis Cache Starter run on arm64?

For Redis Cache Starter, an arm64 image is published; amd64 is image published.

Does Redis Cache Starter need configuration before it starts?

No. The template fills in its own defaults.

Which database does Redis Cache Starter bundle?

The template includes Redis, running as its own service.

Which ports does Redis Cache Starter use?

Redis Cache Starter listens on port 3000 inside the stack.

Where does Redis Cache Starter keep its data?

In a named volume: redis_cache_data mounted at /data.

Can I deploy Redis Cache Starter 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 Cache Starter, 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-alpine, node:22-alpine is what you deploy there.

levelrail-cli templates deploy redis-cache-starter --name my-redis-cache-starter