Skip to content
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

build(devcontainer): enable local development via jekyll serve #255

Merged

Conversation

petermetz
Copy link
Member

  1. Added a VSCode dev container definition that contains Ruby and Jekyll
  2. Declared the gem dependencies so that bundle install can be used to
    install the build dependencies which then enable jekyll serve to locally
    host and render the themed version of the TOC website.
  3. This will unlock easier modification to the theme which is a pre-condition
    of being able to debug CSS/theme/styling changes such as the width issues
    I discovered recently on the new project dashboard page where the last few
    columns are cut off from the view.

Signed-off-by: Peter Somogyvari peter.somogyvari@accenture.com

1. Added a VSCode dev container definition that contains Ruby and Jekyll
2. Declared the gem dependencies so that `bundle install` can be used to
install the build dependencies which then enable `jekyll serve` to locally
host and render the themed version of the TOC website.
3. This will unlock easier modification to the theme which is a pre-condition
of being able to debug CSS/theme/styling changes such as the width issues
I discovered recently on the new project dashboard page where the last few
columns are cut off from the view.

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is file needed to be checked in?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tkuhrt It's optional, but recommended to have it check in because it pins down the dependency versions used (instead of the default auto-upgrades which enable supply-chain attacks where someone takes over an open source project and then starts pushing new releases with malware).

@tkuhrt tkuhrt requested a review from ryjones June 3, 2024 18:15
@ryjones
Copy link
Member

ryjones commented Jun 3, 2024

I don't object to it, but I don't think I would use it.

@ryjones ryjones merged commit 238ab4f into hyperledger:gh-pages Jun 5, 2024
2 checks passed
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.

None yet

3 participants