nix-beam-flakes VS devshell

I left it vague because I didn't want to seem self-promotional. Unmerged documentation branch is the best starting place here: README, docs folder of that branch, example from develop. I daily drive it at work, and on a personal project for about 8 months. Doesn't do well for monorepos with disparate BEAM versions yet, but there are escape hatches and usage-as-library too. For the typical Phoenix project with a few extra system deps it's a pretty good onramp. perSystem.beamWorkspace.devShell.extraPackages is how you add arbitrary buildInputs like your VIPS stuff and .extraArgs for additional arguments to mkShell, such as your non-sensitive envvars. There's a page for future goals too. Publishing the rendered docs as a static site is in my TODOs, it's mostly glue left.

numtide/devshell is cool little extension to bare devshells, you may wanna have it.

There is also devshell[1] which allows you to configure specific commands for your `env` and sits inside your flake.

[1]: https://github.com/numtide/devshell

devshell is pretty useful too :)

I'm new to the Nix world, but so far I've come across Divnix's Digga, Numtide's DevShell, and Misterio77's nix-starter-configs.

How does it differ from https://github.com/numtide/devshell ?

But take a look at devshell is like the NixOS/HomeManager of your (any language) project. I over abused it to create YAML files and to use Nim as script

Here's an example with devShell as a remote repository: sh nix-shell -p '(import (fetchGit "https://github.com/numtide/devshell") {}).cli'