I am working with flakes to enable reproducible builds and development envs amongst my team of developers at work. I have managed to set up an internal binary cache, and I want to have a script that runs nix-copy-closure on the “devShell” store path so that once it’s built it’s available to other team members. Is there a nix command that provides the store path of the current dev shell? Or is it available from nix flake info?
1 Like
Each devShell has a inputDerivation
, as in devShells.whatever.inputDerivation
, that you can use to get a store path that can be used as a copy argument, build target, gcroot, etc.
2 Likes
So I could develop an app on the flake with that command where I could run nix run .#publishDevEnv
is that the pattern?
1 Like
That piece is very subjective, but what you describe sounded like it could work.
1 Like