devbox icon indicating copy to clipboard operation
devbox copied to clipboard

Package Management: Lock a shell's packages using a Devbox lockfile

Open Lagoja opened this issue 3 years ago • 0 comments

Current State

Right now, if Developer A shares a devbox.json with Developer B, Developer B may get different packages installed when they run devbox shell. This can happen when Developer B has a different Nix store or revision configured on their local machine.

Developers do not currently have a way to pin their Devbox to a specific revision or store, so there is no way to guarantee that a shell will work the same way across any two developers

Proposed State

Developers can "lock" or "pin" their shell via the Devbox CLI, which will save the current store and revision that was used to create the shell to a file that can be checked into source control. This file could ensure that a devbox shell will always have the same packages over time, or between developers.

Lagoja avatar Sep 08 '22 23:09 Lagoja