-
Notifications
You must be signed in to change notification settings - Fork 28
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
rough draft of quick-start/flesh out USAGE.md #207
base: branch-24.06
Are you sure you want to change the base?
Conversation
Co-authored-by: Bradley Dice <[email protected]>
What are the specific hardware and system requirements to run RAPIDS devcontainers? |
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.
Made some comments, but will review more later.
Co-authored-by: Paul Taylor <[email protected]>
This isn't polished yet, so I'd say only review it if you really want to. I'm going to take a break and come back to it a little later with fresh eyes.
|
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.
Partial review since I won't get back to this until next week.
Thanks for the clarifications, @harrism! Co-authored-by: Mark Harris <[email protected]>
Co-authored-by: Mark Harris <[email protected]>
* Fix mambaforge shell history (rapidsai#219) * disable history when restoring shell options * Update devcontainer-feature.json * login to dockerhub so we don't hit rate limits
* Update to sccache v0.7.7 (rapidsai#228) * Fix `devcontainer-utils-vault-s3-init` for `[email protected]` (rapidsai#229)
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.
Flushing a couple more comments. I really would like this PR to become reality. It's a lot to read. I wonder if the launch-devcontainer.sh should be moved to a separate PR and merged ASAP, seems useful.
Co-authored-by: Mark Harris <[email protected]>
I'd like to get sign-off from at least @trxcllnt. It is a lot to read, but I think that's because it documents several use cases. I can break it up into chunks if it makes review easier. @bdice wrote the launch script, originally called "rapids-dev" - Brad, do you have thoughts on the name here? Is it OK with you to copy the script here? |
This is fine! I'm happy with |
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.
Generally all looks good. I support merging this after @trxcllnt has a chance to review.
This needs to be retargeted to 24.06. @msarahan After retargeting, could you respond to Paul's review and re-request another round of feedback? |
No description provided.