Home

boring / v2

publicBoring-Software-Inc/v2
Overview Code History Branches Pull requestsIssuesInsights Campfire Docs
main
HomeOverview Code PRsIssues

fix(deploy): add forge-opengit to the Dockerfile manifest copies

2 months ago

3ac6514
Authored
grim8/23/2026, 10:34:05 AM
The image build still failed after the last fix, with two errors instead of
three: apps/api and apps/worker, both of which legitimately depend on
@tripwire/forge-opengit.

Each Dockerfile copies workspace manifests ONE BY ONE before installing, so the
install layer caches until a dependency moves. forge-opengit is a new package
and was never added to those lists, so at install time the directory did not
exist in the image and bun could not resolve a workspace dependency pointing at
it. Local installs always worked because the directory is right there.

Added to all three (api, worker, web) next to forge-github.

Why I missed it: I searched for a Dockerfile with -maxdepth 2 and concluded the
repo had none. They live at apps/*/Dockerfile, one level deeper, and
.dockerignore even says the build context is the monorepo root. I diagnosed the
root workspace dependency from the error text instead of reading the build, and
that dependency WAS one of the three errors, which made a partial fix look like
the whole one.

Verified by building, not by reading: all three images build end to end on bun
1.3, the version that failed, and both apps import the package at runtime
inside their own image.

Parentcee2322

3 files changed
  • apps/api/Dockerfile+1−0
  • apps/web/Dockerfile+1−0
  • apps/worker/Dockerfile+1−0