-
Notifications
You must be signed in to change notification settings - Fork 3
local dev env setup process fixes #226
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: master
Are you sure you want to change the base?
Conversation
Set docker to use yarn 4 so it does not default to yarn 1 update_build was refereing to 'gulp update' but update task is not defined, so i make it target build instead
…re copying package.json to prevent conflicts
…arn version management, preparing Yarn 4.12.0 for use.
…epack, ensuring compatibility with Yarn 4.12.0.
…atibility with Yarn 4.12.0.
…version management.
cbobach
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comments, especially the one for the build/start.sh script. That's the blocker I have. The rest is nice 🙇 💪
package.json
Outdated
| "serve": "gulp build && hugo server --source=website/ --bind=0.0.0.0", | ||
| "build": "gulp build", | ||
| "update_build": "gulp update", | ||
| "update_build": "gulp build", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As gulp update isn't implemented and yarn update_build isn't used anywhere we could scrap this command and update the README.md to run docker exec -it gateway-api-docs yarn build instead of utilizing the yarn update_build command, which isn't implemented 🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| "update_build": "gulp build", |
And then update the README.md
thejspr
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tested it locally and it works well
…README to simplify local serving instructions and modified start.sh to run the Docker container directly for serving the application.
Fixed /build/start.sh — removed the nested Docker command
Set docker to use yarn 4 so it does not default to yarn 1 update_build was referring to 'gulp update' but update task is not defined, so i make it target build instead
Also force docker hub to use latest yarn version