tajniak81andClaude Opus 5
ee4ac441be
The project has no public installs, so there is nothing to migrate from. MigrateLegacyFile, the file-backed Store it read through, PLUGINS_FILE and the legacy path threaded through the Server all go. What is left is one store, PocketBase, and a plugins package that touches no filesystem at all. That was the last thing keeping api_data alive, so the volume goes too. All four compose files now declare exactly one volume, pb_data, and the standalone API Server compose declares none - it talks to an external PocketBase and has nothing of its own to keep. Backing up the stack is backing up one path again. Both images get simpler for it. The API Server image loses VOLUME /data and the su-exec entrypoint that existed only to fix a mounted volume's ownership, so it goes back to a plain USER app; its working directory is now /app and holds nothing. The AIO image loses its second volume and chowns only /pb/pb_data. One consequence worth stating plainly, because it is a small regression rather than a no-op. The panel's Settings -> PocketBase and Settings -> Web App screens write .env in the working directory, which is now ephemeral. In the multi-container stack that changes nothing: compose sets all five of those keys as container environment, and loadDotEnv only applies a key that is not already set, so the file could never win a restart there anyway. In the AIO image it did win for POCKETBASE_ADMIN_EMAIL/_PASSWORD, which are not in that container's environment - so a service account fixed from the panel now lasts only until the container is recreated. Both READMEs say so. Moving those two screens into the app_settings singleton would close it properly; the PocketBase URL and credentials cannot follow, since they are how the database is reached in the first place. go build, go vet and go test ./... pass; the compose files parse and each resolves to a single pb_data volume. Not verified: no Docker CLI here, so neither image was built. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
56 lines
2.2 KiB
Docker
56 lines
2.2 KiB
Docker
# syntax=docker/dockerfile:1
|
|
|
|
# --- Build stage -------------------------------------------------------------
|
|
# Compile a static Go binary. The Vue panel is pre-built into internal/api/dist
|
|
# and embedded via //go:embed, so no Node toolchain is needed here.
|
|
FROM golang:1.26-alpine3.24 AS build
|
|
|
|
WORKDIR /src
|
|
|
|
# Cache module downloads separately from the source for faster rebuilds.
|
|
COPY go.mod ./
|
|
# go.sum is optional (stdlib-only module today); copy it if present.
|
|
COPY go.su[m] ./
|
|
RUN go mod download
|
|
|
|
COPY . .
|
|
|
|
# CGO_ENABLED=0 produces a static binary that runs on a bare alpine image. The
|
|
# entry point is the cmd/server package.
|
|
RUN CGO_ENABLED=0 GOOS=linux go build -trimpath -ldflags="-s -w" -o /out/api-server ./cmd/server
|
|
|
|
# --- Runtime stage -----------------------------------------------------------
|
|
FROM alpine:3.24
|
|
|
|
# HTTPS calls to PocketBase need CA certificates; tzdata for correct timestamps.
|
|
RUN apk add --no-cache ca-certificates tzdata
|
|
|
|
# Run as an unprivileged user.
|
|
RUN addgroup -S app && adduser -S -G app app
|
|
|
|
COPY --from=build /out/api-server /usr/local/bin/api-server
|
|
|
|
# The server keeps no state on disk: plugin settings, like everything else, live
|
|
# in PocketBase. The working directory is only where a .env would be read from
|
|
# at startup if one were mounted, which is a local-development convenience — in
|
|
# Docker every setting arrives as an environment variable. So no volume, and
|
|
# nothing to make writable beyond the image layer itself.
|
|
RUN mkdir -p /app && chown app:app /app
|
|
WORKDIR /app
|
|
|
|
# Config comes entirely from environment variables (see .env.example).
|
|
# POCKETBASE_ADMIN_EMAIL / _PASSWORD are optional at startup: without them the
|
|
# server still runs and a superadmin can configure the connection from the panel.
|
|
ENV API_ADDR=:8080
|
|
EXPOSE 8080
|
|
|
|
# Liveness only: /healthz answers 200 as soon as the process is serving, and
|
|
# does not depend on PocketBase, so a database outage does not mark the
|
|
# container unhealthy. Lets compose gate dependants on condition: service_healthy.
|
|
HEALTHCHECK --interval=30s --timeout=5s --start-period=20s --retries=3 \
|
|
CMD wget -qO- http://127.0.0.1:8080/healthz >/dev/null 2>&1 || exit 1
|
|
|
|
USER app
|
|
|
|
ENTRYPOINT ["/usr/local/bin/api-server"]
|