Skip to content

Cache-mount the pnpm store in the Docker build#6

Merged
theNEXlevel merged 1 commit into
mainfrom
chore/pnpm-store-cache
Jul 4, 2026
Merged

Cache-mount the pnpm store in the Docker build#6
theNEXlevel merged 1 commit into
mainfrom
chore/pnpm-store-cache

Conversation

@theNEXlevel

Copy link
Copy Markdown
Contributor

Adds a BuildKit cache mount (id=pnpm-store, --store-dir=/pnpm/store) to both pnpm install steps (deps + builder) so the content-addressable store persists across builds and is shared with other C4G apps (va-partners, va-stats) on the same BuildKit instance.

Why: the Coolify deploy server has slow/flaky registry egress; a warm shared store lets installs reuse already-downloaded packages instead of re-fetching everything each build.

Mirrors the verified change in va-partners. No runtime behavior change.

🤖 Generated with Claude Code

Shares a warm, content-addressable pnpm store (id=pnpm-store) across C4G
app builds on the same BuildKit instance so slow/interrupted installs on
the deploy server reuse already-downloaded packages. Applied to both the
deps and builder install steps.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@theNEXlevel theNEXlevel merged commit 15c9ab7 into main Jul 4, 2026
1 check passed
@theNEXlevel theNEXlevel deleted the chore/pnpm-store-cache branch July 4, 2026 06:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant