Installation
Run Lasso RPC Core from the released container, or build it from source. For a hosted endpoint instead, use the Lasso Cloud quickstart.Container
ghcr.io/jaxernst/lasso-rpc publishes native Linux AMD64 and ARM64 images;
versions and evidence lists the v0.8.0 image
digest. The release’s Compose file needs Docker Compose, plus OpenSSL to
generate local secrets:
.env across restarts and keep it
private; it contains the signing and Erlang distribution secrets. Compose passes
its values into the container, including provider credentials you add. Changing
.env requires container recreation with docker compose up -d --force-recreate --wait; reloading YAML does not change a running container’s environment.
Compose binds port 4000 to localhost, runs as UID/GID 10001:10001, and keeps the
root filesystem read-only. /tmp is temporary; the named /data volume retains
profiles and benchmark history. docker compose down retains that volume;
docker compose down --volumes deletes it. Set LASSO_PORT in .env to choose
another local port and LASSO_NODE_ID to give the instance a stable identity.
From source
Prerequisites
- Elixir: 1.18.4 (CI version)
- Erlang/OTP: 28 (CI version)
- Node.js: 18+ (asset compilation)
Setup
http://localhost:4000. Dashboard at http://localhost:4000/dashboard.
The included public profile uses free public providers, so no API keys are
needed.
.env File
Lasso loads a .env file from the project root if present (via Dotenvy). System environment variables take precedence over .env values.
Configure and verify
Keepconfig/profiles/public.yml: routes without a profile use public. The
health endpoint shows the application is up; an RPC request like the one above
shows an upstream answers.
For your own profiles, image verification, upgrades and rollback, see
Docker deployment. Core has no built-in client
authentication, so protect exposed RPC, metrics and dashboard endpoints at
your network or reverse proxy.