From 92a69fdb35f7b558381190dfcd1d355c8a2a84dc Mon Sep 17 00:00:00 2001 From: mkelvers Date: Mon, 20 Apr 2026 17:56:22 +0200 Subject: [PATCH] fix: remove stale create-user docker build --- Dockerfile | 2 -- README.md | 2 +- cmd/README.md | 1 - 3 files changed, 1 insertion(+), 4 deletions(-) diff --git a/Dockerfile b/Dockerfile index d843123..86e19f1 100644 --- a/Dockerfile +++ b/Dockerfile @@ -29,7 +29,6 @@ RUN templ generate # Build the server and CLI tools RUN go build -o main_server ./cmd/server -RUN go build -o create_user ./cmd/create-user FROM debian:bullseye-slim @@ -42,7 +41,6 @@ RUN apt-get update && apt-get install -y ca-certificates sqlite3 && rm -rf /var/ RUN mkdir -p /app/data COPY --from=builder /app/main_server . -COPY --from=builder /app/create_user . COPY --from=builder /app/static ./static COPY --from=builder /app/dist ./dist COPY --from=builder /app/migrations ./migrations diff --git a/README.md b/README.md index 5881632..72d3a01 100644 --- a/README.md +++ b/README.md @@ -131,7 +131,7 @@ When the server starts, the app is available at `http://localhost:3000`. Important notes: - Environment variables are read directly from the process environment (`PORT`, `DATABASE_FILE`, `ENV`, `PLAYBACK_PROXY_SECRET`); `.env` is not auto-loaded. -- The web app currently exposes a login route only. If your database has no users yet, create the first user outside the web UI. +- The web app currently exposes a login route only. Seed at least one user directly in the SQLite database before first login. For containerized usage, the included `Dockerfile` uses a multi-stage build that installs Bun + templ, builds assets, generates templates, compiles `cmd/server`, and ships a slim runtime image with SQLite support. diff --git a/cmd/README.md b/cmd/README.md index 97eb036..21e289f 100644 --- a/cmd/README.md +++ b/cmd/README.md @@ -3,7 +3,6 @@ Executable entrypoints live here. - `cmd/server`: main web process (`go run ./cmd/server`) -- `cmd/create-user`: admin CLI for adding login users (`go run ./cmd/create-user --email user@example.com --password-stdin`) ## Why this structure