Add Dev Containers config #2255
Open
Conversation
This file contains 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
|
The |
astrojuanlu
force-pushed
the
dev-containers
branch
from
a04bf00 to
6fe1e31
Compare
Signed-off-by: Juan Luis Cano Rodríguez <[email protected]>
Signed-off-by: Juan Luis Cano Rodríguez <[email protected]>
Signed-off-by: Juan Luis Cano Rodríguez <[email protected]>
Signed-off-by: Juan Luis Cano Rodríguez <[email protected]>
Signed-off-by: Juan Luis Cano Rodríguez <[email protected]>
Signed-off-by: Juan Luis Cano Rodríguez <[email protected]>
astrojuanlu
force-pushed
the
dev-containers
branch
from
6fe1e31 to
7939a7c
Compare
|
Aside from my comments above, the Dev Container works. So this is ready for review & merge. |
| "onCreateCommand": "./.devcontainer/onCreateCommand.sh", | ||
|
|
||
| "postStartCommand": { | ||
| "backend": "nohup bash -c 'uv run python package/kedro_viz/server.py demo-project &' > backend.out 2> backend.err < /dev/null", |
There was a problem hiding this comment.
I am a little confused why this happens, from where does it get the build files?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Why was this PR created?
Gitpod has been up until now the preferred way to do QA of PRs without having to build a full development environment.
However, Gitpod Classic is going away, and we need to find another solution.
Gitpod Flex works with Dev Containers https://www.gitpod.io/blog/introducing-gitpod-flex#development-container-support so here is my first attempt to add Dev Containers config.
Development notes
This mostly works. But almost by chance...
The
backendcommand is succeeding. And somehow it's launching both the backend and the frontend? I don't fully understand why ❓I didn't see a
npm installstep anywhere listed in ourCONTRIBUTING.md(hitting #1764 again?) but I added to the dev container anyway, and looks like it's working.When I tried to configure the image to use NodeJS 18 though, I found some inconsistencies between what the IDE tells me and what the standards say.
I would like somebody else to pick this up if it's not too much to ask 🙏🏼
QA notes
https://code.visualstudio.com/docs/devcontainers/create-dev-container
Run the
>dev containers: rebuild and reopencommand and check that everything works.Checklist
RELEASE.mdfile