LiveContext Files

What is new

Self-hosting & install

• Fresh installs start again. Docker Hub now refuses anonymous pulls of the MinIO images, which stopped a new installation before it could start. MinIO is now pulled from its official Quay registry in every compose file (the public one, the npx launcher and the development one), with the same image tags, so existing storage is untouched.

This release also includes everything listed for v0.3.0.

Update an existing install

git pull
docker compose pull
docker compose up -d

The compose file pins this release's image tag, so run git pull first. Your data lives in Docker volumes and is kept across updates.

Fresh install

git clone https://github.com/livecontext-ai/livecontext-ce
cd livecontext-ce
docker compose up -d

Then open http://localhost:3000

Images

Pull from whichever registry you prefer, the digests are identical.

• ghcr.io/livecontext-ai/livecontext-ce:v0.3.1
• ghcr.io/livecontext-ai/livecontext-ce-frontend:v0.3.1
• ghcr.io/livecontext-ai/livecontext-ce-bridge:v0.3.1

• ghcr.io/livecontext-ai/livecontext-ce-screenshot-renderer:v0.3.1 (opt-in renderer profile)

• docker.io/livecontext/livecontext-ce:v0.3.1

• docker.io/livecontext/livecontext-ce-frontend:v0.3.1
• docker.io/livecontext/livecontext-ce-bridge:v0.3.1

• docker.io/livecontext/livecontext-ce-screenshot-renderer:v0.3.1 (opt-in renderer profile)

• quay.io/livecontext/livecontext-ce:v0.3.1

• quay.io/livecontext/livecontext-ce-frontend:v0.3.1
• quay.io/livecontext/livecontext-ce-bridge:v0.3.1
• quay.io/livecontext/livecontext-ce-screenshot-renderer:v0.3.1 (opt-in renderer profile)

Each image is also tagged v0.3, v0 and latest if you prefer to track a moving line rather than pin an exact release.