Front image build sends node_modules because the root .dockerignore does not exclude it #114

What is wrong

The front image is built with the repository root as its context. Docker then applies the root .dockerignore and does not apply front/.dockerignore. The root file does not exclude node_modules, so a checkout with frontend dependencies installed sends those trees to the daemon.

Where

• docker-compose.yml lines 64-66 set the front context to . and the dockerfile to front/Dockerfile.
• profiles/postgres/docker-compose.yml lines 11-13 and profiles/oracle/docker-compose.yml lines 14-16 set the front context to ../.., the repository root, with dockerfile front/Dockerfile.
• The root .dockerignore has no node_modules entry.
• front/.dockerignore lines 2-3 exclude node_modules/ and **/node_modules/. The rest of that file is also unused for these builds, because it is not next to the context root.

A Docker build was not run.

Why it matters

The context includes every installed node_modules directory under the repository. The upload is large, and any later COPY that matches those paths can take the installed tree instead of the lockfile install inside the image.

Smallest fix

Add node_modules/ and **/node_modules/ to the root .dockerignore.

The same root exclusion is required when the component trees are imported into this repository: #105