Deployment

Ilavrita does not enforce authorization, tenancy or audit yet. Deploy it with synthetic data only. See known limitations.

From source

Requires Go 1.27+.

git clone https://github.com/Ilavrita/Ilavrita.git
cd Ilavrita
make bootstrap
make build
./bin/ilavrita serve --http=127.0.0.1:8090 --dir=./ilavrita_data

make bootstrap fetches the pinned embedded-runtime fork. A clone without submodules will not compile, because the replace directive in go.mod has nothing to resolve to.

Container

docker run --rm -p 8090:8090 -v ilavrita-data:/data ghcr.io/ilavrita/ilavrita:latest

Or with Compose:

docker compose up --build

Images are published per release for linux/amd64 and linux/arm64, with build provenance attached.

Configuration

Settings come from the environment. Copy .env.example and edit it; never commit a filled-in copy.

Configuration is not wired up yet; the server currently takes embedded-runtime's own serve flags.

Checking a deployment

curl http://127.0.0.1:8090/healthz
curl http://127.0.0.1:8090/version
curl -H 'Accept: application/fhir+json' http://127.0.0.1:8090/fhir/R4/metadata

/version reports the version and the commit it was built from, which is how a running instance is matched to a source tag.

Production notes

TLS terminates at Ilavrita or at a reverse proxy you trust. Do not expose it without TLS.

The database is a single SQLite file under the data directory, so a backup is a consistent copy of that directory plus any external object storage. Backup, restore and migration tooling does not exist yet, which is one reason this is not a production release.

Ilavrita scales vertically on one node. Horizontal scale is a later phase.