home.social

#snix — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #snix, aggregated by home.social.

fetched live
  1. Fellas, I have 2 months before my next major commitment, my j*b. Wish me luck as I attempt to fully internalize the workings of #nixOS, #nix the language, and nix the pacman. I'd set up a #systemd #nspawnd #container for regular linux work. (I'd like other suggestions on this). My current plans:

    - #flakes/'modern' practices
    - dotfile integration (not using #homemanager)
    - use #bitwarden integration somehow natively and bridging between bitwarden store cloned locally and #linux keystore (not even sure what I mean here)
    - #secureboot that unseals the encrypted root partition keys from the TPM and auto-decrypts my root
    - #nixpak as much
    - package my scripts to be proper packages/flakes/modules/whatever for better integration
    - #snix/ #lix?
    - #dhall config instead?

    Give more suggestions/tips

  2. Fellas, I have 2 months before my next major commitment, my j*b. Wish me luck as I attempt to fully internalize the workings of #nixOS, #nix the language, and nix the pacman. I'd set up a #systemd #nspawnd #container for regular linux work. (I'd like other suggestions on this). My current plans:

    - #flakes/'modern' practices
    - dotfile integration (not using #homemanager)
    - use #bitwarden integration somehow natively and bridging between bitwarden store cloned locally and #linux keystore (not even sure what I mean here)
    - #secureboot that unseals the encrypted root partition keys from the TPM and auto-decrypts my root
    - #nixpak as much
    - package my scripts to be proper packages/flakes/modules/whatever for better integration
    - #snix/ #lix?
    - #dhall config instead?

    Give more suggestions/tips

  3. Fellas, I have 2 months before my next major commitment, my j*b. Wish me luck as I attempt to fully internalize the workings of #nixOS, #nix the language, and nix the pacman. I'd set up a #systemd #nspawnd #container for regular linux work. (I'd like other suggestions on this). My current plans:

    - #flakes/'modern' practices
    - dotfile integration (not using #homemanager)
    - use #bitwarden integration somehow natively and bridging between bitwarden store cloned locally and #linux keystore (not even sure what I mean here)
    - #secureboot that unseals the encrypted root partition keys from the TPM and auto-decrypts my root
    - #nixpak as much
    - package my scripts to be proper packages/flakes/modules/whatever for better integration
    - #snix/ #lix?
    - #dhall config instead?

    Give more suggestions/tips

  4. Fellas, I have 2 months before my next major commitment, my j*b. Wish me luck as I attempt to fully internalize the workings of #nixOS, #nix the language, and nix the pacman. I'd set up a #systemd #nspawnd #container for regular linux work. (I'd like other suggestions on this). My current plans:

    - #flakes/'modern' practices
    - dotfile integration (not using #homemanager)
    - use #bitwarden integration somehow natively and bridging between bitwarden store cloned locally and #linux keystore (not even sure what I mean here)
    - #secureboot that unseals the encrypted root partition keys from the TPM and auto-decrypts my root
    - #nixpak as much
    - package my scripts to be proper packages/flakes/modules/whatever for better integration
    - #snix/ #lix?
    - #dhall config instead?

    Give more suggestions/tips

  5. @katzenmann @nixos_org One of the hurdles is stabilizing an underlying feature like fetchTree. @domenkozar is doing some great work on that with an alternate implementation of it in #SNix, exposing some of the unfortunate choices that all #Nix implementations should backtrack on.

    This may lead to a small change in behavior in Flakes that would not be considered acceptable normally for non-experimental parts of Nix, but will be necessary in order to fix various problems that exist within Flakes.

    For a user of Flakes, this means that you may have to put up with a binary cache miss, or synchronizing your Nix update with your team, but you shouldn't have to overhaul your code or anything.

  6. @katzenmann @nixos_org One of the hurdles is stabilizing an underlying feature like fetchTree. @domenkozar is doing some great work on that with an alternate implementation of it in #SNix, exposing some of the unfortunate choices that all #Nix implementations should backtrack on.

    This may lead to a small change in behavior in Flakes that would not be considered acceptable normally for non-experimental parts of Nix, but will be necessary in order to fix various problems that exist within Flakes.

    For a user of Flakes, this means that you may have to put up with a binary cache miss, or synchronizing your Nix update with your team, but you shouldn't have to overhaul your code or anything.

  7. @katzenmann @nixos_org One of the hurdles is stabilizing an underlying feature like fetchTree. @domenkozar is doing some great work on that with an alternate implementation of it in #SNix, exposing some of the unfortunate choices that all #Nix implementations should backtrack on.

    This may lead to a small change in behavior in Flakes that would not be considered acceptable normally for non-experimental parts of Nix, but will be necessary in order to fix various problems that exist within Flakes.

    For a user of Flakes, this means that you may have to put up with a binary cache miss, or synchronizing your Nix update with your team, but you shouldn't have to overhaul your code or anything.

  8. @katzenmann @nixos_org One of the hurdles is stabilizing an underlying feature like fetchTree. @domenkozar is doing some great work on that with an alternate implementation of it in #SNix, exposing some of the unfortunate choices that all #Nix implementations should backtrack on.

    This may lead to a small change in behavior in Flakes that would not be considered acceptable normally for non-experimental parts of Nix, but will be necessary in order to fix various problems that exist within Flakes.

    For a user of Flakes, this means that you may have to put up with a binary cache miss, or synchronizing your Nix update with your team, but you shouldn't have to overhaul your code or anything.

  9. @katzenmann @nixos_org One of the hurdles is stabilizing an underlying feature like fetchTree. @domenkozar is doing some great work on that with an alternate implementation of it in #SNix, exposing some of the unfortunate choices that all #Nix implementations should backtrack on.

    This may lead to a small change in behavior in Flakes that would not be considered acceptable normally for non-experimental parts of Nix, but will be necessary in order to fix various problems that exist within Flakes.

    For a user of Flakes, this means that you may have to put up with a binary cache miss, or synchronizing your Nix update with your team, but you shouldn't have to overhaul your code or anything.