Self-host Nginx Reverse Proxy (Multi-Backend) on a VPS

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

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

Specification

Status
Listed
Category
Starter Kits
Services
orders, payments, proxy
Ports
80
Volumes
0
Memory
about 192 MiB
arm64
image published
amd64
image published
Settings to fill in
none
License
not yet recorded

About Nginx Reverse Proxy (Multi-Backend)

One Nginx entrypoint routing to two independent backend services, demonstrating depends_on across three services. Runs 3 containers (orders, payments, proxy), with proxy listening on port 80.

What it deploys

Nginx Reverse Proxy (Multi-Backend) runs as 3 services in a single Compose app, listening on port 80.

ServiceImageTagPortsVolumes
orders node 22-alpine none none
payments node 22-alpine none none
proxy nginx 1.27-alpine 80 none

Before you install

  • CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
  • Listed. It is in the catalog. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 80 directly on the host, so open them in the VPS firewall only if you want that.

Settings and environment

You do not have to fill in anything. Values are never shown here.

ServiceVariableValue
ordersNODE_ENVPreset by the template
paymentsNODE_ENVPreset by the template

Install Nginx Reverse Proxy (Multi-Backend) on a VPS

  1. Install Levelrail on a fresh VPS

    Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.

    curl -fsSL https://levelrail.com/install.sh | sudo sh
  2. Sign in

    Open the setup link, choose a password, then log the CLI in. The CLI install command is curl -fsSL https://levelrail.com/install-cli.sh | sh if the machine does not have it. See Getting started.

    levelrail-cli login --device
  3. Read the template

    Shows the entry, including its full compose.yaml.

    levelrail-cli templates get nginx-multi-backend-starter
  4. Deploy it

    This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.

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

Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Nginx Reverse Proxy (Multi-Backend).

More in Starter Kits

All Starter Kits templates