Preserve management container publishing after the monorepo move (#8) #12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-8-management-publish"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #8.
Context
The monorepo-aware Dockerfile and workflow build context/paths were established in #6. This PR closes the remaining gap: making the publish trigger an explicit allowlist so the criterion "trigger only for management, shared deps, workspace lock/config, Docker files, or its workflow" holds precisely.
Change
.forgejo/workflows/build-publish.ymlswitches frompaths-ignore(denylist) topaths(allowlist):apps/management/**(excluding its README, docs, anddocker-compose*.yml)packages/**(excluding package READMEs) — shared workspace packagespnpm-lock.yaml,pnpm-workspace.yaml,package.json,turbo.json.dockerignoreand this workflow fileUnrelated root files, docs, READMEs, store-only changes, and Compose edits no longer publish an image.
Acceptance criteria
.,apps/management/docker/Dockerfile).CMD node scripts/migrate.mjs && node server.js; standalone output includesscripts/,drizzle/, static assets, server files; flat prod deps overlaid for the migrate script).packages/catalogpublish a management image (packages/**).latestimage name (tags unchanged::latestand:${sha}).CONTAINER_REGISTRY_TOKENandNEXT_PUBLIC_BETTER_AUTH_URLhandling preserved.Verification
YAML re-read and structurally valid; management standalone build confirms
scripts/migrate.mjsanddrizzle/migrations land in.next/standalone/apps/management.