helvede.net is one of the many independent Mastodon servers you can use to participate in the fediverse.
Velkommen til Helvede, fediversets hotteste instance! Vi er en queerfeministisk server, der shitposter i den 9. cirkel. Welcome to Hell, We’re a DK-based queerfeminist server. Read our server rules!

Server stats:

169
active users

#nix

12 posts10 participants0 posts today

@ironicbadger & @ChrisLAS - if y’all are going to do a segment on #Immich kiosk, I’d be happy to preemptively share what I’ve got going with it. to;dr is a little pi-sized “digital photo frame” on my desk & a 65” tv near my front door that has digital art via Immich kiosk and a home dashboard that can be switched to with the push of a zigbee button. The TV and an old tiny Lenovo to run it were acquired for free. The Pi one is all #Nix-ified too.

dear internet, i have a nixos with an efi-only partition and i want to do luks unlock via ssh from inside initrd. when setting network settings into `boot.initrd.network` and ssh config (with host keys in /boot/efi) into `boot.initrd.network.ssh`, i do not get any action in stage 1 attempting to either bring up the network nor launch SSH. i get the normal systemd-udev prompt for the luks passphrase. any ideas?
#nixos #nix

Nice, lib.packagesFromDirectoryRecursive now supports nested scopes!

packagesFromDirectoryRecursive transforms a directory tree of packages into a nested attribute set of derivations. You can use it to manage a package set in a similar way to by-name in nixpkgs (without the sharding part). The package files in tree must be suitable for callPackage.

Subdirectories in the tree result in nested attribute sets. In the following example, packages d, e and f will be in a nested attribute set called my-namespace.

my-packages
├── a.nix
├── b.nix
├── c
│ ├── my-extra-feature.patch
│ ├── package.nix
│ └── support-definitions.nix
└── my-namespace
├── d.nix
├── e.nix
└── f
└── package.nix

Previously, this would only use one scope (my-packages), so e could only depend on d as my-packages.d. With the introduction of nested scopes, e can refer to d within the same scope directly.

PR: github.com/NixOS/nixpkgs/pull/

function doc on noogle (which isn't yet updated for the new behavior): noogle.dev/f/lib/packagesFromD

Supersedes #359984, as the author isn't responding. I squashed in the fixup commits (had to split them up as they wouldn't apply) and resolved merge conflicts with master.
Original PR descr...
GitHublib.packagesFromDirectoryRecursive: use explicit recursion, support nested scopes by katexochen · Pull Request #392800 · NixOS/nixpkgsBy katexochen
Replied in thread

We are hosting the 10th iteration (I forgot to toot about the previous one) of our Brussels #Nix / #NixOS / #Guix User Group Meetup next Friday, March 28th, at @HSBXL!

The lightning talks planned so far are:
- Local DNS server with CoreDNS by Hugo
- Self-hosting a Mastodon instance by @xavier and myself :)

Want #cloudnative but with the power of #declarative configuration? The recoverability of #transactions for system configuration?

Wednesday it's the online #guix meet-up! With a great talk by @paulbutgold
about running docker / oci containers using the Guix configuration system.

His Gocix project has #prometheus, #grafana, #forgejo, #conduit and #traefik examples.

Meet-up details:

meetup.com/guix-social/events/

#nix#linux#oci

on to the next #nix puzzle

(for arbitrary nixos system configuration including disko-based declarative partitioning, how to enable generating *both* test VMs and installers? the obvious answer would seem to be "nixos-generators" but `nixosGenerate { format = "vm-nogui"; ... }` ignores disko configuration inside the `...`.)

Replied in thread

@eliasp While I know what you mean, I strongly disagree with that truncation.

First, the nixos hardware module needs to exist & support all of your particular hardware. This isn't a given thing depending on the HW you are about to use.

Secondly, there are still too many settings you need to do manually such as xfce environments, lots of app settings, ...

I started with NixOS in the naïve assumption that it is allowing me to define everything across all of my computers. I failed miserably & with the next opportunity, I'll switch back to Debian.

However, if you're totally open to let the #NixOS community to choose the hardware platform (devices that do have a HW config module which supports all features), desktop environment (sway?) and all apps for you, then you're probably fine with "everything in your #Nix configuration". If not, you do spread misleading vibes here - so to say.

And yes, there's still the issue with not being to run #Python in a normal way.

HTH