Self-host Nginx Reverse Proxy (Multi-Backend) with Levelrail

One Nginx entrypoint routing to two independent backend services, demonstrating depends_on across three services.

  • Memory192 MiB
  • Archarm64
  • Services3

How to self-host Nginx Reverse Proxy (Multi-Backend)

  1. Pull the images

    3 images are pulled on your server.

    Show images
    • node:22-alpine
    • node:22-alpine
    • nginx:1.27-alpine
  2. Create the app

    3 services start in a single Compose app, on port 80.

  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.

Nginx Reverse Proxy (Multi-Backend) requirements

Memory
About 192 MiB
Architectures
amd64 image published, arm64 image published
Ports
80
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 80 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 Nginx Reverse Proxy (Multi-Backend). 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 Nginx Reverse Proxy (Multi-Backend) docs page.

Deploy Nginx Reverse Proxy (Multi-Backend) your way

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

Deploy Nginx Reverse Proxy (Multi-Backend) from the CLI

levelrail-cli templates deploy nginx-multi-backend-starter --name my-nginx-multi-backend-starter

Deploy Nginx Reverse Proxy (Multi-Backend) 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/nginx-multi-backend-starter/deploy

Nginx Reverse Proxy (Multi-Backend) configuration

Nginx Reverse Proxy (Multi-Backend) services

ServiceImagePortsVolumes
orders node:22-alpine none none
payments node:22-alpine none none
proxy nginx:1.27-alpine 80 none

Nginx Reverse Proxy (Multi-Backend) environment variables

VariableServiceValue
NODE_ENV orders Preset by the template
NODE_ENV payments Preset by the template

Ports and volumes

Ports
80
Volumes
none

Nginx Reverse Proxy (Multi-Backend) FAQ

How much memory does Nginx Reverse Proxy (Multi-Backend) need?

The catalog lists about 192 MiB of memory for Nginx Reverse Proxy (Multi-Backend) across its 3 services.

Does Nginx Reverse Proxy (Multi-Backend) run on arm64?

For Nginx Reverse Proxy (Multi-Backend), an arm64 image is published; amd64 is image published.

Does Nginx Reverse Proxy (Multi-Backend) need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Nginx Reverse Proxy (Multi-Backend) use?

Nginx Reverse Proxy (Multi-Backend) listens on port 80 inside the stack.

Can I deploy Nginx Reverse Proxy (Multi-Backend) 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 Nginx Reverse Proxy (Multi-Backend), 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 node:22-alpine, node:22-alpine, nginx:1.27-alpine is what you deploy there.

levelrail-cli templates deploy nginx-multi-backend-starter --name my-nginx-multi-backend-starter