You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the monorepo example specifically, we see dist already exists before we are shown the Dockerfile. No problem, I can assume I can add that in the Dockerfile in a prior step to running pnpm deploy.
If there is a .gitignore file in the application directory then any files listed here are ignored.
Going back to the monorepo example, we see a .gitignore. The output, dist, will obviously be in this. So... won't that example simply... fail? pnpm deploy will not even copy dist because it is ignored, no?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Guide: https://pnpm.io/docker#example-2-build-multiple-docker-images-in-a-monorepo
For the monorepo example specifically, we see dist already exists before we are shown the Dockerfile. No problem, I can assume I can add that in the Dockerfile in a prior step to running
pnpm deploy.What immensely confuses me is the last section at the bottom of the page for
pnpm deploy:Going back to the monorepo example, we see a .gitignore. The output, dist, will obviously be in this. So... won't that example simply... fail?
pnpm deploywill not even copy dist because it is ignored, no?Beta Was this translation helpful? Give feedback.
All reactions