Docker

The image the repository publishes

ghcr.io/voxmastery/fluctlightdb is the image named in the repository. The commands below are copied from docs/DOCKER.md. They were not pulled, built, or started while this page was written. A local image build needs Rust 1.88.

The published quick start

The image listens on 8792. The entrypoint requires FLUCTLIGHT_API_KEYS in the form tenant:key:role, creates a tenant brain under /data on first start, and execs fluctlight serve. Binding is 0.0.0.0 inside the container, which is what the -p mapping reaches. Building that image locally is a different command in the same document, and it was not run either.

From docs/DOCKER.md. Not executed for this page.

docker pull ghcr.io/voxmastery/fluctlightdb:latest

docker run -d --name fluctlight \
  -p 8792:8792 \
  -e FLUCTLIGHT_API_KEYS=default:your-secret-key:write \
  -v fluctlight-data:/data \
  ghcr.io/voxmastery/fluctlightdb:latest

Talking to it

The same document shows a Python client, FluctlightClient.from_env(), aimed at FLUCTLIGHT_SERVE_URL. That client was not run. The routes it would call, POST /api/v1/experience and POST /api/v1/activate, are the two stable HTTP routes. There is no checkpoint route. The Node page is the same HTTP surface from TypeScript, also unread against a live server.