Skip to content

fix: keep vendor/ on the host instead of a named volume - #15

Merged
tyrsson merged 1 commit into
0.1.xfrom
fix/vendor-volume-bind-mount
Aug 24, 2026
Merged

fix: keep vendor/ on the host instead of a named volume#15
tyrsson merged 1 commit into
0.1.xfrom
fix/vendor-volume-bind-mount

Conversation

@tyrsson

@tyrsson tyrsson commented Aug 24, 2026

Copy link
Copy Markdown
Member

Problem

The \ ooling\ service mounted \�endor:/app/vendor\ as a named volume. That hid dependencies from the developer's host tree (no \�endor/\ visible in the working copy) and forced all Composer I/O through the Docker Desktop VM layer, pegging the CPU during installs.

Change

The container is only a test runner: \�endor/\ is now part of the plain .:/app\ bind mount, so the host copy is the single source of truth. Only the \composer-cache\ named volume remains.

Matches the updated webware-tools alignment preset (webinertia/webware-tools@feb2e49) and the verified fix in webware-log PR #61.

  • \docker compose config --quiet\ passes
  • Verified pattern in webware-log: 86 tests OK with host-owned vendor

The container is only a test runner. A vendor:/app/vendor named volume hid
dependencies from the developer's host tree and forced Composer I/O through
the Docker Desktop VM layer. vendor/ is now part of the plain .:/app bind
mount; only the composer-cache named volume remains.
@codecov

codecov Bot commented Aug 24, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@tyrsson
tyrsson merged commit 037ee8e into 0.1.x Aug 24, 2026
11 checks passed
@tyrsson
tyrsson deleted the fix/vendor-volume-bind-mount branch August 24, 2026 23:22
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