devenv

I got really excited when Farid showed me this! He has fixed the oldest and most upvoted issue on devenv: https://github.com/cachix/devenv/issues/16 Basic example in devenv: { multiverse, ... }: { packages = [ multiverse.cmake."3.16.5" multiverse.bun."0.7.0" ]; } Docs: https://devenv.sh/pinning/#pinning-an-individual-package-ver...

We've removed telemetry a long time ago, see https://github.com/cachix/devenv/issues/1733

Yes, still sending the data is bad. Their docs [1] do not mention the generate command can take an exclusion argument [2]. Maybe the dot (.) for current directory will exclude everything, but that may defeat the purpose. If the current directory were the default, and on first run an error message like "Please include files first" appeared--and users also must enter "Y" at a disclaimer message--they could explicitly opt in instead. And that should be placed before the tar-n-upload piece. The pull request was also merged before approval. Github branch protection could have been set to require at least one approver. [1] https://devenv.sh/blog/2025/02/13/devenv-14-generating-nix-d... [2] https://github.com/cachix/devenv/blob/main/devenv/src/cli.rs...

No even worse, it sends the actual file content to the server. Linked in the post: https://github.com/cachix/devenv/blob/6c987a8795eedea872afe4...

I've just tried both `devenv` and `flox`, and the latter had two related niceties: - Direnv wants to put its config inside the root of a git repo, which makes it hard to ignore. Flox's config is all in a `.flox` directory, so I could `echo * >> .flox/.gitignore` in any repo without changing the repo's gitignore. - There seems to be no way to run `direnv` on an environment that's not the current working dir, see https://github.com/cachix/devenv/issues/67. OTOH, `flox` was a bit harder to install in an existing nix setup and requires trusting their cache, at least if I wanted to do a cached install. You can follow the instructions in https://flox.dev/docs/install-flox/#__tabbed_1_6, or you could add yourself to Nix's "trusted users" (which makes sense only if you're the only user on the computer using Nix). See also https://github.com/flox

I'm of the mindset that NixOS is too much, all at once. I understand the power of the Nix ecosystem, but the barrier of entry remains too high to enter. I've switched to using devenv[1] as a first step. This at least allows me to experiment with using nix to configure my dev environment in a per directory fashion, while allowing me to use the Linux distro of my choice. [1]: https://github.com/cachix/devenv

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. https://github.com/cachix/devenv/issues

> but worried that the development is not moving forward There is an open v1.0 PR: https://github.com/cachix/devenv/pull/1005

This looks really great! When do you expect to add Linux support? Until then, I'm using a devenv.sh Nix-based setup (without mDNS), with something like this: https://github.com/cachix/devenv/blob/main/examples/mkcert/d...

For python, you could just install bare python with venv and/or poetry and manage your dev python dependencies outside nix. For eg. if you were using devenv.sh, there is an example here: https://github.com/cachix/devenv/tree/main/examples/python-p...

You can see how it's used in the GitHub actions of devenv: It calls `devenv ci` (which checks that the devenv file is good), then runs a 'script' in the devenv file... https://github.com/cachix/devenv/blob/8bea91cd1073b0d51cf96e... The 'script' in the devenv file: https://github.com/cachix/devenv/blob/8bea91cd1073b0d51cf96e...

I've been hacking on VSCode integration as of yesterday, follow https://github.com/cachix/devenv/issues/26 for updates :) This shouldn't be more than a day of work.