-
Notifications
You must be signed in to change notification settings - Fork 124
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
Add scrypto dev container target #2004
base: release/cuttlefish
Are you sure you want to change the base?
Conversation
8ff2571
to
5f14446
Compare
Docker tags |
5f14446
to
3276dac
Compare
Benchmark for 0696ac2Click to view benchmark
|
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.
Really nice!
Out of interest:
- How is this supposed to be used?
- Do people add some kind of devcontainer file to their repo?
- How can this be tested locally during development?
- How have you been testing it?
- Might we want some script to build the dev container locally, possibly commented in the Dockerfile to help future people to tweak it?
- Perhaps we need something in CI to test the building of this target? Like the dev-container equivalent of
ci-scrypto-builder.yml
andpublish-scrypto-builder.yml
Dockerfile
Outdated
@@ -50,6 +50,13 @@ WORKDIR /app | |||
|
|||
RUN cargo install --path ./radix-clis | |||
|
|||
FROM base-image as dev-container | |||
RUN apt install -y bash-completion powerline |
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.
Might be worth a quick comment explaining that this installs a better prompt for a better dev experience (with maybe a link to the powerline website?)
RUN echo 'powerline-daemon -q; POWERLINE_BASH_CONTINUATION=1; POWERLINE_BASH_SELECT=1; . /usr/share/powerline/bindings/bash/powerline.sh; . /etc/bash_completion' >> ~/.bashrc | ||
COPY --from=builder /app/target/release/scrypto /usr/local/bin/scrypto | ||
COPY --from=builder /app/target/release/resim /usr/local/bin/resim | ||
RUN rustup target add wasm32-unknown-unknown |
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 wonder if we want some kind of ENTRYPOINT
line? Possibly not! What's standard for dev containers?
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.
The documentation shows no examples with an ENTRYPOINT
My intention is to create another repo with the Hello template in and that uses this image as it's dev container
Build the image with {
"name": "Radix Scrypto",
"image": "scrypto-dev-container",
"customizations": {
"vscode": {
"extensions": [
"rust-lang.rust-analyzer",
"tamasfe.even-better-toml",
"radixpublishing.radix-developer-tools"
]
}
}
}
That would be the same for the new repo also containing a Hello template
Will add this
Will add this too |
cda17ea
to
44da993
Compare
44da993
to
5aebfa9
Compare
Summary