Just a juicy bit for folks that happen to use #just and #nix and want them to play together...

If your #nixflake outputs `devShells.default`, you can use a nix shell to run your Justfile tasks as script recipes, e.g.:

```justfile
set script-interpreter := ['nix', 'develop', '--command', 'bash']
set unstable := true

[script]
my_job:
echo "this runs *inside* a dev shell"
````

Actual use in context:
https://github.com/alerque/polytype/commit/0289eb2

I find it rather weird that defining your  #NixOS machine in your flake via `inputs.mynixpkgs.lib.nixosSystem` is *not* enough to have it actually use your `mynixpkgs`. No, you need to do this boilerplate stunt. Why doesn't it do it automatically? 🤔

https://gitlab.com/nobodyinperson/nixconfig/-/commit/274f4265f37e5256ede5cd8f0fc5054ba4f408d2

#nixFlake #nix

I have no idea what I fucked up, but it seems that somewhere in the last 4 commits I made it so that my computer is now stuck on the #Plymouth splash screen and #GDM is not showing up. Quiting plymouth allows me to reach a tty.

Any #NixOS pros here willing to help a poor soul out, please?

https://github.com/filipdutescu/yggdrasil

#Nix #NixFlake #NixFlakes #Flake #Flakes #Disko #Linux #GNOME

Argh, trying to install a custom package on my #nixos it's only temporary but thought others might want to use it to, so why not a #NixFlake ? ...how hard can it be to create a simple flake that adds one package to a system I thought, 2 hours in so far...

Seems like guides either only show the remote flake side or the system flake side, but no combination of examples works so far. Also some syntax changes last year and most guides still refer to the old syntax apparently.

why the fucking fuck is `nix flake update` followed by `sudo nixos-rebuild switch --flake .#mylaptopsredactedhostname` not updating my systempackages

i can plainly see vscode is at 1.86.2 in the nixos-unstable branch, and my flake.nix is using that branch, and yet I'm still stuck on 1.85.1

#nixos #nix #nixflake

So... Is there no "NixOS-er" way to setup bridge networking with #libvirtd, but for the one from the wiki?

I could really use a #Nix way to setting that up instead of doing the whole write my own bridge network config and running commands manually 😅

#NixOS #NixFlake #NixFlakes #libvirt

@cbleslie Thanks for responding. I realize I stuff multiple apps in a #nixFlake, but I can't figure out an incantation for an app that runs tools from the *build* dependencies against the *sources* and outputs the artifact(s):

```console
$ git clone -b ldoc https://github.com/alerque/sile
$ cd sile
$ nix develop
$ configurePhase
$ make lua-api-docs
```

This generates a folder of HTML docs I want to output via `nix run <repo>#dump-lua-api-docs` without making the build tools part of the default app.

A question for #nix folks: I have a FOSS project with a working #nixflake that runs the app and also has devShells setup correctly with all the developer tooling.

The project itself has a `make` target to generate documentation. I would like to expose this documentation to flake consumers such that `nix run path/to/flake ... something` could be used to generate and expose (output?) the documentation files.

I can't wrap my head around what code I should reach for to create a features like this.