-
Notifications
You must be signed in to change notification settings - Fork 352
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
Composing devenv.yaml #14
Comments
i'm coming from a conda-centric data science experience. i really want this to work! i've been looking for ways to create composable environments. |
I have a devenv file in my home dir / repo, and a bunch of task-specific environments in subdirs. They all want to track nixpkgs independently while I'd like to just track it once at the top level. Would this help with that? My current workaround is to have each devenv.yaml point to the inputs:
nixpkgs:
url: nixpkgs ( which on my systems is set to the registry.nixpkgs.to = {
owner = "NixOS";
repo = "nixpkgs";
rev = inputs.nixpkgs.rev;
type = "github";
}; ) Other than not being as clean as referencing the input used at the repo root, the downside is the lock files still need to be updated individually for each subdir when the registry entry is updated. |
Getting around to experimenting with devenv. Like the above comment, I'm interested in hoisting shared configuration to a single place, and then consuming that in a number of repositories. For example, in this higher-up shared environment configuration, I have something that checks for Extending that, I tried to setup something similar for Terraform. i.e. if there are any
Presumably, this could be an input at the top level and propagated downstream if |
Please leave a thumbs up if you'd like to see this happen and a comment with your use case.
The text was updated successfully, but these errors were encountered: