Nix / NixOS

1783 readers

1 users here now

Main links

Videos

founded 1 year ago

MODERATORS

erlingur

ballmerpeaking

WhiteBlackGoose

Help Me With My Baby Nix Dev Environment (mander.xyz)

submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/nix

7 comments fedilink hide all child comments

Hi all Nix experts,

I recently started using nix to manage my dev environment on my immutable distro, and I need some help.

I was wondering if I am using a large package like TexLiveFull, how to make sure nix don't delete large packages after I close the shell? I also don't want this package to be available in my global environment, as I don't need to use it outside vscode.

Another question is how to keep my packages up-to-date. I don't do serious development work, thus I typically perfer my package and dev-tools to be on the latest version. I prefer to have a little management of this as possible. Ideally, every time I start up a nix shell, the package manager will grab the latest version of the package if possible without requiring additional interaction from me. Is this possible?

Finally, is there any way to bubblewrap programs installed by nix to only access the file within the starting path of the shell? I don't imagine this is possible, but it would definitely be nice if nix has some security feature like this.

Thanks in advance for your help! I understand parts of this post might be ridiculous. I am still new to nix. Please correct me if I am not using nix in the "correct" way.

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

[–] qqq 4 points 9 months ago* (last edited 9 months ago) (1 children)

I was wondering if I am using a large package like TexLiveFull, how to make sure nix don’t delete large packages after I close the shell? I also don’t want this package to be available in my global environment, as I don’t need to use it outside vscode.

There's a bunch of tools that solve this problem.

https://github.com/direnv/direnv/wiki/Nix

In the link above check out the table in the "Some factors to consider" section. However, note that it hasn't be updated since May 30, 2022. Many of those tools don't depend on direnv if you don't need its functionality.

Personally, I use direnv and enable nix-direnv using these options:

https://search.nixos.org/options?channel=23.11&from=0&size=50&sort=relevance&type=packages&query=direnv

Here's an example of how I use direnv with nix-direnv.

Edit: damn over wrote what I wrote to the first question with a response to the second question. Thank goodness for automatic file backups I have setup in Emacs.

[–] [email protected] 2 points 9 months ago* (last edited 9 months ago) (1 children)

Hum, I personally do not enjoy adding an additional parties of trust by adding direnv, nix-direnv, and homemanager to my workflow.

But all of these project seems rather well maintained, and probably homemanager can help me manage my vscodium as well, so that might be good.

[–] Corbin 3 points 9 months ago (1 children)

direnv is small enough that you can manually audit it by reading the source code. nix-direnv is also small enough for this, and conceptually it is a replacement for direnv's builtin Nix support.

You don't need home-manager yet, and you can put it off for a while; it's mostly useful if you want to instantiate a homedir on multiple machines.

[–] [email protected] 2 points 9 months ago* (last edited 9 months ago)

Thank you so much for your insight. I personally feel like home-manager is a worth-while investment, since it supports auto-update and managing my vscode setting; both are pretty appealing to me. In the future, I might use it to manage my global packages like libreoffice and vscodium (assuming it won't kill my process during auto update?).

At this point, I will probably go with never running nix gc, but I will try to properly set everything up after couple weeks.