Nix / NixOS

1932 readers

1 users here now

Main links

Videos

founded 2 years ago

MODERATORS

erlingur

ballmerpeaking

WhiteBlackGoose

Tear down script for Nix develop (feddit.org)

submitted 1 week ago by [email protected] to c/nix

7 comments fedilink hide all child comments

I'm working on small nix flake to standardize the developer environments at my job.

What I'm still missing, however, is a way to clean up after leaving the shell. Some hook to call a shell script, when the shell is closed.

Is there something like this? I thought about wrapping the actual nix develop call inside a bash script and waiting for nix to terminate, but that seems rather hacky.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago) (1 children)

In this case what I would recommend is to provide a command (perhaps inside that nix develop) that would set up all the images/services/data, and a second one to tear it down, and allow devs to run those commands themselves. This allows for more flexibility, e.g. multiple nix develop shells of the same project, but only one does the stateful stuff, coming back to the same shell later in the day without waiting for the setup. Most importantly it would allow for easy clean-up if the shell is shutdown unexpectedly and doesn't have time to clean up itself, e.g. SIGKILL or power loss. It can be as simple as using writeShellScriptBin to string together commands (instead of doing it in the shellHook as you presumably are doing right now), or as complex and flexible as https://github.com/svanderburg/nix-processmgmt .

Then, if you really want to automate it, you can simply add your-setup-command and trap "your-cleanup-command" EXIT to your shellHook.

[–] [email protected] 1 points 1 week ago

I would externalize it into a separate script/command anyway (the skeleton already exists).

However, knowing myself, I would certainly forget cleaning up manually once in a while. My goal was to create truly self-contained, stupid-simple dev environments - or get as close as possible to it.