-
Notifications
You must be signed in to change notification settings - Fork 2k
With dockerfile update #10550
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
With dockerfile update #10550
Conversation
…ng for old dockerfiles
…ng for old dockerfiles
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@kessenma is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
I'm trying to use this with pnpm and running into many issues. Can you try it out and fix those? Thank you. |
Ok I'll look into it some more with a fresh install and pnpm. I'll also update the testing steps above so they're written with better testing steps. I'll comment back here when I'm done. |
…in the readme.md
Description
added in support for using npm, pnpm, and yarn dockerfiles via a use-dockerfile.js script. directions are in the readme.md
Testing Instructions
Give a quick description of steps to test your changes.
1 run the following scripts from the turborepo/examples/with-docker/package.json:
use-pnpm-dockerfile
use-pnpm-dockerfile
use-pnpm-dockerfile
2 check that the with-docker/package.json and see if the "packageManager" (line 27) was updated to match pnpm/npm/yarn
3 check that the dockerfiles inside the project are now configured with pnpm/npm/yarn
4 ensure that the old Dockerfile's were archived in these folders:
turborepo/examples/with-docker/apps/api/archived-docker-file
turborepo/examples/with-docker/apps/web/archived-dockerfile