Run CE with Docker

Use Docker to run a self-hosted browser workspace without installing the frontend and backend toolchains. The container needs a reachable database and persistent storage if you want to retain login sessions across replacement.

Start a local instance#

docker run -d \
  --name whodb \
  -p 127.0.0.1:8080:8080 \
  -v whodb-data:/data \
  clidey/whodb:latest

Open http://localhost:8080. This example binds browser access to the local machine and keeps the session data in a named volume. Use a specific published image tag when the deployment needs a fixed version.

Give the container a database route#

For a database in the same Compose network, use its service name and internal port in the connection form. For a database on the host, use the host address supported by your Docker setup.

Do not enter localhost for a database running outside the WhoDB container. Test the host and port from the container's network if the connection times out.

For SQLite or DuckDB, mount the directory containing the database file and enter its container path. Certificate paths in connection profiles also refer to files inside the container, so mount those files when required.

Preserve sessions and configure access#

Keep /data across container replacements. If you explicitly set WHODB_ENCRYPTION_KEY, retain that same key as well. Losing the stored session data or its encryption key means users need to connect again.

For remote access, configure the intended network boundary and HTTPS. Set WHODB_SECURE=true when serving over HTTPS. Server-configured profiles can be used by anyone who reaches the instance, so use database credentials appropriate for that audience.

Check that it works#

GET /health checks whether the WhoDB process is available. Open the connection page and connect to a development database to verify the separate database path. Inspect a known table and run a small read query.

See Installation for Compose, configuration variables, and port examples, then follow First connection.