Host on Render

Render builds a Dockerfile from your repository and runs it as a web service.

Build

wisp deploy init render       # render.yaml, and a Dockerfile if there is none

render.yaml is a blueprint with one web service on the docker runtime, named for your package, with WISP_SECRET set to generateValue: true. The Dockerfile is the one wisp build --docker writes. --force replaces the file.

Deploy

Commit both files and push. In Render choose New, Blueprint and pick the repository. Render builds the Dockerfile and sets PORT, which the app listens on.

Environment

WISP_SECRET is generated for you by the blueprint; to set your own, use the service's environment settings.
Other variables: Environment variables.

Limits

The image is the Docker one: epoll instead of io_uring under Docker's default profile.
WebSockets and streaming work, as in any container.

Files and Data

static/ and the styles are inside the binary.
Saved tables live in /data inside the container. The blueprint does not attach storage, so rows are lost with the instance unless you mount a persistent disk at /data or use a custom store (Where rows are kept).

Host with Docker, Deploying.

Is This Page Useful?

Edit This Page