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

Modularize git repo support #4

Open
harrism opened this issue Apr 29, 2020 · 2 comments
Open

Modularize git repo support #4

harrism opened this issue Apr 29, 2020 · 2 comments

Comments

@harrism
Copy link
Contributor

harrism commented Apr 29, 2020

Currently rapids-compose clones a fixed set of repos. Most users are RAPIDS developers, and often they work on a different subset of those repos. So there's a lot of overhead on the initial cloning, but also whenever you re-run make init.

It would be nice to first select which RAPIDS repos you want to work with. It would also be nice to be able to "turn off" repos that are already cloned, perhaps by rerunning make init.

@trxcllnt
Copy link
Owner

Agreed. The static nature of docker-compose.yml makes this non-trivial, but I should be able to work around that with some docker-in-docker magic.

@jrhemstad
Copy link

Similarly, it would be nice if you opt out of a project the conda environment solver would ignore the conda environment of that project. I frequently run into issues where projects have incompatible conda environments.

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

No branches or pull requests

3 participants