devbox
devenv
Our great sponsors
devbox | devenv | |
---|---|---|
47 | 88 | |
7,349 | 3,359 | |
4.8% | 13.9% | |
9.7 | 9.8 | |
6 days ago | 6 days ago | |
Go | Nix | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
devbox
-
Show HN: Flox 1.0 – Open-source dev env as code with Nix
How does Flox compare to Devbox? https://github.com/jetpack-io/devbox
- Instant, easy, and predictable development environments on any machine
-
PackagingCon – a conference only for software package management
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.
-
NixOS and My Descent into Insanity
> 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.
-
TySON: a native go library that lets you use TypeScript as an embedded configuration language without depending on Node or V8
Also devbox ( https://github.com/jetpack-io/devbox ) which is what this is for does not work on windows because of its Nix dependency.
-
Simplifying preview environments for everyone
For these reasons, I believe most developer environments should prioritize developer experience over fidelity. Tools like Containerized development environments and cloud emulators can strike the right balance and there’s no surprise that we see increased activity around devcontainers, and similar solutions.
-
Codespaces but open-source, client-only, and unopinionated
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.
-
Why did Nix adopt Flakes?
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:
-
NixTest: a tiny unit testing framework written in pure nix
As part of the work we've been doing with [devbox](https://github.com/jetpack-io/devbox), we needed a unit testing framework to test some of our nix code. Unfortunately we had some use cases where we did *not* want to introduce a dependency on `nixpkgs` (and therefore we couldn't use `runTests`).
-
Docker's deleting Open Source images and here's what you need to know
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
devenv
-
Fast, Declarative, Reproduble and Composable Developer Environments Using Nix
I gave devenv multiple tries, and I am sorry to say there are multiple annoying issues that forced me to give up every time.
Some of these 200+ issues are unsolved for a fairly long time.
-
Nix – A One Pager
Software developers often want to customize:
1. their home environments: for packages (some reach for brew on MacOS) and configurations (dotfiles, and some reach for stow).
2. their development shells: for build dependencies (compilers, SDKs, libraries), tools (LSP, linters, formatters, debuggers), and services (runtime, database). Some reach for devcontainers here.
3. or even their operating systems: for development, for CI, for deployment, or for personal use.
Nix provision all of the above in the same language, with Nixpkgs, NixOS, home-manager, and devShells such as https://devenv.sh/. What's more, Nix is (https://nixos.org/):
- reproducible: what works on your dev machine also works in CI in prod,
- declarative: you version control and review your configurations and infrastructure as code, at a reasonable level of abstraction,
- reliable: all changes are atomic with easy roll back.
-
Show HN: Lapdev, a new open-source remote dev environment management software
https://devenv.sh/ and nix in general are great for setting up dev environments.
-
Show HN: Flox 1.0 – Open-source dev env as code with Nix
> but worried that the development is not moving forward
There is an open v1.0 PR: https://github.com/cachix/devenv/pull/1005
-
What's the Next Vagrant?
2) A way to run services apps depend on (databases, job runners, cache etc).
I am going to suggest one of the Nix based tools that do those things:
- https://devenv.sh/ (I use this at work)
-
Ask HN: How can I make local dev with containers hurt less?
Yup, I haven’t tried it but there is https://devenv.sh which is built on top of nix and makes it simple.
-
Flakes aren't real and cannot hurt you: using Nix flakes the non-flake way
Although Guix reads better than Nix (after all, it's Lisp), I found the support and resources available for learning severely lacking.
Plus, you have to jump through hoops to install non-free software, which goes against the ethos of Guix anyway.
IMHO, Nix is clearly "the winner" here and we'll see more and more adoption as it improves. Lots of folks are doing exciting work (see https://determinate.systems/, https://devenv.sh/, https://flakehub.com/). And the scale and organization around nixpkgs is damn impressive.
-
NixOS has one fatal flaw
I don't think you can ever get Nix as simple as PNPM, simply because native libraries are sometimes annoying, need to be configured at build time to a greater degree and because the problem space it attacks is so much larger than PNPM, which only deals with the JS/Node.js ecosystem.
However, I do think that there exist reasonable levels of abstraction that sacrifice some expressive power for simplicity and such systems could maybe expose a PNPM-like CLI. One example that comes to mind is devenv.nix [1]. While it doesn't yet have a CLI, its configuration file is YAML and relatively simple. I think there's more to be done in this space and I hope for tools that are easier to grasp in the future.
> Nix package files evaluate down to configuration for the Nix package manager, but I haven’t ever seen a good explanation for the basic essentials underneath all the abstraction. Every guide I’ve learned from and all the package defs I’ve read seem to cargo cult many layers of mysterious config composing config. Without easy to learn essentials it’s difficult to grok the system as a whole.
To me it sounds like the essential that you're referring to is the 'derivation' primitive, which is almost always hidden behind the mkDerivation abstraction from nixpkgs. This [2] blog post is an exploration of what exactly that means.
I'd also love for the documentation situation to be much better, in particular in terms of official, curated resources. But I'm not convinced that you actually need to know the difference between derivation and mkDerivation to make effective use of Nix, because in practice you would always use the latter. That said, mkDerivation and the whole of nixpkgs is essentially a huge DSL (I believe this is what you meant when you said 'config composing config') that you do need to know and is woefully underdocumented.
> I would love to adopt Nix for developer tooling for Notion’s engineers, but today it’s about infinity times easier to work around the limitations mentioned of Docker+Ubuntu+NPM than to work around the limitations of Nix.
One approach I have taken to is to specify the environment in Nix, but then generate Docker devcontainers from it, so most people don't come into contact with Nix if they don't want to.
[2] https://ianthehenry.com/posts/how-to-learn-nix/derivations/
-
Development Environments with Guix, similar to devenv.sh
This though, through the use of devenv.sh, which uses nix, as when I got into nix I though it was going to be easier to just make a development environment, not the case. Until I found devenv.sh, I could actually finally make good environments... It also has other features like containers and services, which also help me know that I can get the most of it if the time comes.
-
devenv needs help testing 1.0 release
Instructions: https://github.com/cachix/devenv/pull/745
What are some alternatives?
devpod - Codespaces but open-source, client-only and unopinionated: Works with any IDE and lets you use any cloud, kubernetes or just localhost docker.
nix-direnv - A fast, persistent use_nix/use_flake implementation for direnv [maintainer=@Mic92 / @bbenne10]
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
direnv - unclutter your .profile
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
devshell - Per project developer environments
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
nix - Nix, the purely functional package manager
rembg - Rembg is a tool to remove images background
podman - Podman: A tool for managing OCI containers and pods.
deequ - Deequ is a library built on top of Apache Spark for defining "unit tests for data", which measure data quality in large datasets.