3 ms·
I've spent the last year managing all my packages with Devbox (https://github.com/jetpack-io/devbox https://github.com/jetpack-io/devbox). Local dev, cloud dev
by mikenikles 3y ago
I've spent the last year managing all my packages with Devbox (https://github.com/jetpack-io/devbox https://github.com/jetpack-io/devbox).
Local dev, cloud dev, CI, production – all with the same config file. Fingers crossed my talk submission for PackagingCon gets accepted. It'd be awesome to share this new way of working with a wider audience.
- mdaniel 3y agoI see this in almost every thread on this topic, but feel it buries the lede since its dependency upon nix makes it more complicated than it seems, at least every time I've revisited it. Maybe it's an artifact of its 0.x version, or the fact that I have improper expectations With regard to your "CI" use case, this is part of why I said I must have improper expectations because $ docker run --name dbox ubuntu:22.04 bash -c 'curl -fsSL https://get.jetpack.io/devbox | FORCE=1 bash; devbox init; devbox add awscli2; devbox add zulu@11' $ docker exec dbox du -hs /nix 4.1G /nix and that's just the simple version, on Linux, and thus is likely the happy-path in CI. When trying to use it locally on macOS, this here is just some "you wanna do _what_?!": https://github.com/DeterminateSystems/nix-installer/tree/v0.10.0/src/action/macos https://github.com/DeterminateSystems/nix-installer/tree/v0.... (not to pick on determinate.systems, the upstream is similarly facepalm: https://nixos.org/manual/nix/stable/installation/installing-binary#macos-installation https://nixos.org/manual/nix/stable/installation/installing-... )