Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. I have a big flake that manages my home-manager, nix-darwin (work), and nixos (home).

I have a big flake that manages my home-manager, nix-darwin (work), and nixos (home).

Scheduled Pinned Locked Moved Uncategorized
nixnixos
4 Posts 3 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • nemith@hachyderm.ioN This user is from outside of this forum
    nemith@hachyderm.ioN This user is from outside of this forum
    nemith@hachyderm.io
    wrote last edited by
    #1

    I have a big flake that manages my home-manager, nix-darwin (work), and nixos (home). Problem is that often times getting all these to work on -unstable is "fun" with a single flake.lock file.

    Has anyone done a flake.nix/flake.lock _per_ host and did something like the Dendritic pattern to include modules? This way i can bump systems independently as needed?

    It's not perfect, but maybe better than waiting weeks to get the perfect nixos-unstable that works across all systems and allows me to debug/patch separately.

    #nix #nixos

    jakehamilton@hachyderm.ioJ craigbro@infosec.exchangeC 2 Replies Last reply
    0
    • nemith@hachyderm.ioN nemith@hachyderm.io

      I have a big flake that manages my home-manager, nix-darwin (work), and nixos (home). Problem is that often times getting all these to work on -unstable is "fun" with a single flake.lock file.

      Has anyone done a flake.nix/flake.lock _per_ host and did something like the Dendritic pattern to include modules? This way i can bump systems independently as needed?

      It's not perfect, but maybe better than waiting weeks to get the perfect nixos-unstable that works across all systems and allows me to debug/patch separately.

      #nix #nixos

      jakehamilton@hachyderm.ioJ This user is from outside of this forum
      jakehamilton@hachyderm.ioJ This user is from outside of this forum
      jakehamilton@hachyderm.io
      wrote last edited by
      #2

      @nemith have you tried adding multiple inputs for the different channels? I don't see a reason why a separate flake would be needed to pull in more than one channel.

      nemith@hachyderm.ioN 1 Reply Last reply
      0
      • jakehamilton@hachyderm.ioJ jakehamilton@hachyderm.io

        @nemith have you tried adding multiple inputs for the different channels? I don't see a reason why a separate flake would be needed to pull in more than one channel.

        nemith@hachyderm.ioN This user is from outside of this forum
        nemith@hachyderm.ioN This user is from outside of this forum
        nemith@hachyderm.io
        wrote last edited by
        #3

        @jakehamilton I could do that. I just like the idea of 'nix flake update` per system better than trying to manage a bunch of weirdly name input channels.

        1 Reply Last reply
        0
        • nemith@hachyderm.ioN nemith@hachyderm.io

          I have a big flake that manages my home-manager, nix-darwin (work), and nixos (home). Problem is that often times getting all these to work on -unstable is "fun" with a single flake.lock file.

          Has anyone done a flake.nix/flake.lock _per_ host and did something like the Dendritic pattern to include modules? This way i can bump systems independently as needed?

          It's not perfect, but maybe better than waiting weeks to get the perfect nixos-unstable that works across all systems and allows me to debug/patch separately.

          #nix #nixos

          craigbro@infosec.exchangeC This user is from outside of this forum
          craigbro@infosec.exchangeC This user is from outside of this forum
          craigbro@infosec.exchange
          wrote last edited by
          #4

          @nemith single flake lock, multiple pkgs as input to modules. Then i can use pkgs (stable) or bleed-pkgs (unstable) in my modules as appropriate. Signal and FFox from unstable, for example, and the rest defaults to stable..

          1 Reply Last reply
          1
          0
          • R relay@relay.infosec.exchange shared this topic
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups