Skip to content
LinkPeek Documentation

Docker Image Deployment

The hoseiny/linkpeek image packages the Go server, static assets, and realtime hub in one container. Use this approach when you need a fast sandbox or when CI pipelines must spin up LinkPeek temporarily.

Terminal window
docker pull hoseiny/linkpeek:latest

Tags follow semantic versions (v1.0.x) plus latest. Pin a version tag in production to avoid accidental upgrades.

Terminal window
docker run \
--name linkpeek \
-p 9009:9009 \
-e LINKPEEK_ADMIN_PASSWORD="change-me" \
-e DATA_DIR=/data \
-v $(pwd)/linkpeek-data:/data \
hoseiny/linkpeek:latest
VariablePurpose
LINKPEEK_ADMIN_PASSWORDShared credential for the web UI and API. Rotate immediately after first login.
DATA_DIRAbsolute path for payload uploads, capture transcripts, and PDF exports.
REALTIME_ENABLEDSet to 0 to disable the WebSocket hub when debugging.
CLOUDFLARED_ENABLEDSet to 1 if you plan to attach the Cloudflared sidecar manually.

Rotate credentials

Never expose the container with the bootstrap admin password. Rotate it via the dashboard before sharing access with teammates.

  1. Browse to https://localhost:9009/ and log in.
  2. Rotate the admin password within the Access panel.
  3. Add the payload, capture, and retry labs to your bookmarks.
  4. Configure persistent backups for the mounted DATA_DIR volume.

For automated tests, wrap the container in docker compose or your CI orchestration and clean up with docker rm -f linkpeek after each suite.