What does HackerNews think of devbox?

Instant, easy, and predictable development environments

Language: Go

#1 in Maven
I've spent the last year managing all my packages with 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.

> Now to figure out what a "flake" is…

Flake is a worthwhile addition to Nix that is worth learning. But like anything Nixian, it's not straightforward.

Have you checked out any of the tools that aim to simplify Nix experience? We built Devbox (https://github.com/jetpack-io/devbox) with this in mind.

Local first, cloud optional is the only way (IMHO) we're going to get people off their local laptop development setups.

We need to support local dev environments first, with the exact same config a developer can then move to the cloud.

See https://github.com/jetpack-io/devbox for how this can be achieved and https://www.mikenikles.com/blog/dev-environments-in-the-clou... for my thoughts after 3 years of working in this space.

If you like the properties of Nix, but find it confusing, you should check out Devbox! It simplifies the process of creating Nix-powered dev environments:

https://github.com/jetpack-io/devbox

Nix is a great option for reproducible dev environments. However, the Nix language is pretty complex, which can make adoption and buy in tough.

One solution that my company is working on is Devbox, which tries to provide the usability of tools like Yarn or Brew with the reproducibility of Nix.

You can check us out at https://github.com/jetpack-io/devbox

You might be interested in Devbox (http://jetpack.io/devbox)! We built Devbox because we were frustrated with our Docker based dev environments, and our goal is to provide the power of Nix with a more accessible interface (similar to yarn or other package managers).

We're open source and rapidly adding features, you can check us out on Github at https://github.com/jetpack-io/devbox

checkout https://github.com/jetpack-io/devbox

> Devbox is a command-line tool that lets you easily create isolated shells for development

it uses nix, and they just added

`devbox global`

> Devbox Global allows you to add packages to a global devbox.json. This is useful for installing a standard set of tools you want to use across multiple Devbox Projects. You can also use Devbox Global to install and manage packages on your Host OS, as a substitute for tools like brew or apt-get.

https://github.com/jetpack-io/devbox/releases/tag/0.4.0

Tools like Devbox: https://github.com/jetpack-io/devbox are making this way easier. Devbox is powered by nix, but it hides all of the complexity and makes it easier to use.
Depending on your use case, devbox (https://github.com/jetpack-io/devbox) could be what you're looking for. It is powered by Nix, but abstracts the nix language away, so that you can use it like a "regular" package manager.

Currently it works on a "per-project" basis, but we're planning to add support to use it as your primary package manager for global installs as well.

If you are looking for a simple interface that is an alternative to asdf, but uses Nix under the hood, you could check out Devbox (https://github.com/jetpack-io/devbox). Our goal is to make spinning up per-project dev environments easy and approachable, without having to write a full nix.flake.
Another take: DevBox provides 60% of the features of Docker while being faster and simpler. https://github.com/jetpack-io/devbox

It provides filesystem isolation -- it uses Nix under the covers. This is great if you're a dev and don't want to mess with routing ports across a hidden VM to the host, just run a command and your service appears directly on the host.

DevBox allows very rapid development. And for production, it exports to Docker. You get the best of all worlds!