Self-host Static Site + API Backend on a VPS

A static frontend and a separate API service deployed together, the split most SPAs actually run.

levelrail-cli templates deploy static-site-api-starter --name my-static-site-api-starter

Specification

Status
Listed
Category
Starter Kits
Services
api, static
Ports
4000, 80
Volumes
0
Memory
about 128 MiB
arm64
image published
amd64
image published
Settings to fill in
none
License
not yet recorded

About Static Site + API Backend

A static frontend and a separate API service deployed together, the split most SPAs actually run. Runs 2 containers (api, static), with api listening on port 4000.

What it deploys

Static Site + API Backend runs as 2 services in a single Compose app, listening on ports 4000, 80.

ServiceImageTagPortsVolumes
api node 22-alpine 4000 none
static 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 ports 4000, 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
apiNODE_ENVPreset by the template

Install Static Site + API 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 static-site-api-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 static-site-api-starter --name my-static-site-api-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 Static Site + API Backend.

More in Starter Kits

All Starter Kits templates