Host on Railway

Railway builds a Dockerfile from your project and runs it as a service.

Build

wisp deploy init railway      # railway.toml, and a Dockerfile if there is none

railway.toml sets the builder to DOCKERFILE with Dockerfile as the path, and a restart policy of ON_FAILURE with 10 retries. The Dockerfile is the one wisp build --docker writes. --force replaces the file.

Deploy

railway up

Railway builds the Dockerfile and sets PORT, which the app listens on. Or point a service at the repository.

Environment

WISP_SECRET: 32 or more random characters, in the service's variables, for an app that signs cookies.
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, so give that path storage that outlives a deploy, or use a custom store (Where rows are kept).

Host with Docker, Deploying.

Is This Page Useful?

Edit This Page