Prototype configuration of a devcontainer to speed up dev-env configuration#8
Merged
trivikr merged 3 commits intonodejs:mainfrom Aug 8, 2024
Merged
Conversation
trivikr
approved these changes
Aug 8, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The concept and usage are explained here: https://github.com/cspotcode/node-code-ide-configs/tree/node-devcontainer/.devcontainer#readme
VSCode lets you describe how to run within a dockerized dev environment. VSCode will mount a host directory into the container and run the editor experience within the container. For example, the editor's integrated terminal runs inside the container.
This configuration leverages that feature to quickly give you:
make -j4should take about 2mins the first time, not an hourThe image can be built either from scratch or by starting with a previously-built image. The idea is that a CI automation could efficiently keep this image up-to-date with the latest master by rebuilding nightly.
I'm opening this PR to get eyes on the idea and to see if anything similar has been attempted in the past.