home.social

#flakes — Public Fediverse posts

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

fetched live
  1. Well, this is kind of neat. 's has support for . I was not expecting that. 😅

    I still package all my things with , like a madman. Still. It is nice to see these featured adoptions like this. 😎

    railpack.com/languages/gleam

  2. Multi-platform outputs should be the most basic thing a flake does. Yet,, the common answer was to pull in flake-utils/flake-parts: an extra input, a limited "default systems" list from a third-party repo, and pinned copies piling up in nested lock files.

    Meanwhile, builtins.mapAttrs over nixpkgs.legacyPackages covers every platform nixpkgs supports — with zero inputs. Since August 2026, `nix flake init` gives you exactly this.

    How it works & how to extend it:
    nixcademy.com/posts/new-defaul

    #Nix @nixos_org #Flakes

  3. Unity, AMILI launch Asian gut microbiome-inspired synbiotics

    The product, AMILI Metabolic Health, is already available in selected practitioner channels and will be available in Unity via an exclusive retail arrangement from September 2026. A key feature of the product is that it was formulated based on Asian gut microbiome da…
    #dining #cooking #diet #food #Nutrition #dietary #flakes #nutrition
    diningandcooking.com/2773877/u

  4. @tomgag I agree. Thanks for speaking up. There is much positive feedback about the move to ban LLM code on . It risks strengthening liberal big tech by leaving it dominant. I use LLMs to help build tested that run my machines, yet I now worry my fleet setup processes using codeberg could be ruined by other's decisions. That is why dependence on large platforms is risky & this move has proven this. I use & as a backup for Codeberg as it is flaky.

  5. @yisraeldov
    Now if we make the flake.nixosModules.somename : {arg1, arg2} = {}
    Then we can start composing too.

    In short: it's a very neat approach to modularize the options which scales better.

    Those who are using nix flake-parts and dendritic pattern, feel free to correct me or simplify this please.

    #nix #flakes #nixos #homemanager #nixhomemanager #flake-parts #dendritic #dendriticpattern

  6. Who here does flake reviews??

    (Please I've already been ghosted once by someone whose review I was really looking up to 🥲)

    codeberg.org/innocentzer0/nix-

    #nix #nixos #flakes #flakesarentreal

  7. Kurze Frage bzgl. #NixOS und #flakes:

    "sudo nix flake update --flake /etc/nixos/" wurde ausgeführt. Ein "nix flakes info" bringt u.A. das Bild im Anhang. Führt mich ein Update der Inputs also zu einem Stand von vor 6 Tagen für nixpgks?
    Ich würde ja erwarten, dass ich zumindest ein tagesaktuelles Bild sehen würde

  8. So, I gave #devenv a try.

    I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works.

    But, while #devenv configs are composable locally, they can't import a remote config as #flake does.

    Also, `devenv shell` breaks my #tmux / #nvim setup where my #flake works like a charm.
    So, yeah, I'll keep my #flake for now.
    At work and at home.

    CC @Ilygad

  9. Nyt taisin löytää kaikkien aikojen kaninkolon, mitä linux on mulle tarjoillut. Ajattelin kesäprojektina päivittää oman NixOS flaken noudattamaan dendritic flake -logiikkaa ja sen seurauksena ajauduin denful-projektin nettisivuille. Saattaa olla, että kirjottelenkin flaken suoraan den-logiikan mukaiseksi nyt kun sain perus (lue: raakile) dendritic flaken toimimaan oikein. #NixOS #flakes #denful #Linux

  10. NixOS - Das Multi-Host-Setup individualisieren

    In meinem letzten Beitrag der NixOS-Reihe zeige ich, wie man einen einzelnen Rechner aus dem gemeinsamen Setup herauslöst und individuell konfiguriert – ohne die anderen Rechner auch nur zu berühren.

    #NixOS #Nix #Flakes #Nix_Store #Linux

    gnulinux.ch/nixos-das-multi-ho

  11. NixOS - Major-Upgrade, Pakete aus 'unstable' einbinden und "Wegwerf-Pakete"

    Ein Major-Update steht an. Zudem binden wir Programme aus dem Rolling-Release-Zweig ein – und nutzen Software, ohne sie überhaupt zu installieren.

    #Nix #NixOS #Flakes #Linux

    gnulinux.ch/nixos-major-upgrad

  12. RE: social.tchncs.de/@innocentzero

    So far, it's going good! I'm using the default way of installing packages for now, and also using the graphical installer. I'll probably first get a hardware-configuration.nix that uses labels instead of UUIDs, and preferably a prettier mapper name than luks-<insert-UUID-here>. I still need to do this through the calamares installer, and I'll migrate to CLI for everything once I'm done with my #flakes setup

    #nixos #nix

  13. 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

  14. NixOS - Multi-User-Setup einrichten

    Weitere Benutzer werden anlegt – am Beispiel eines Gastnutzers und einer neuen regulären Benutzerin. Nebeneffekt des heutigen Setups: Heute wird nochmal ganz klar, welche "Nixe" für was zuständig ist.

    #Nix #NixOS #Flakes #Linux

    gnulinux.ch/nixos-pakete-aus-u

  15. NixOS - Codeberg-Kommunikation optimieren und Troubleshooting

    In diesem Teil optimieren wir die Kommunikation mit Codeberg, so dass keine Passwörter mehr eingegeben werden müssen. Git- und Codeberg-Troubleshooting inklusive.

    #Nix #NixOS #Flakes #Git #Codeberg #Linux

    gnulinux.ch/nixos-multi-user-s

  16. NixOS - Setup-Guide, Teil 3

    Im abschließenden Teil zeige ich, wie man in nur je 30 Minuten weitere eigene Rechner mit der vorhandenen NixOS Konfiguration von Null an aufsetzt und mit Codeberg synchron hält.

    #Nix #NixOS #Flakes #Linux

    gnulinux.ch/nixos-setup-guide-

  17. NixOS - Setup-Guide, Teil 2

    In diesem Teil geht es darum wie Starkoch NixOS wirklich zum Sternekoch wird. Wie man die Integration anderer Köche vorbereitet und wie die Speisekarte gesichert wird.

    #NixOS #Nix #Flakes #Linux

    gnulinux.ch/nixos-setup-guide-

  18. So I'm re-writing my NixOS config to use flake-parts right?

    It accidentally came up using Nouveau/NVK and I legitimately did not even notice.

    I gamed.

    #nix #nixos #flakes #nvidia #nvk #nouveau #wow

  19. Thinking about flake-parts, kinda wanting to implement it, but it's kinda intimidating.

    #nix #nixos #flakes

  20. NixOS - Setup-Guide, Teil 1

    Das ist der Auftakt zu einem dreiteiligen Set-up-Guide. Es geht bei Null los und endet in einem Multi-Host-Set-up. Im Teil 1 beschreibe ich die NixOS-Idee, also den brillanten Paradigmenwechsel, sowie erste Schritte für Ein- und Umsteiger.

    #NixOS #Nix #Flakes #Linux

    gnulinux.ch/nixos-setup-guide-

  21. A month ago I wanted to switch to #Helix and immersed myself in #HomeManager, #Flakes, #sops-nix, and #colmena. Today, after a long redesign of my #NixOS module structure, I successfully applied colmena to the first test node. Twelve more will follow. This OS is wild.

  22. Announcing #GratisOffice today, a "Vanity Office suite" of mine:
    - Its free-as-in-freedom first
    - source-only (that is: no binaries provided, you have to build it yourself)
    - proudly forked from @CollaboraOffice (and thus indirectly also #LibreOffice)
    - equally happy to have its commits and patches upstreamed to either of them with proper attribution under the MPLv2
    - also aiming to soon create a trivially easy build environment on _all_ of #Linux using #nixos #flakes
    - all details can be found in the README: codeberg.org/bjoern-michaelsen

    #CollaboraOnline

  23. We're finally configuring Wireguard - but we only get a third of the way there in this blog post. Lots of exciting option config stuff tho, and a new blog feature which lets me interrupt myself.

    https://blog.xvrqt.com/nix-wireguard-proxies-pt-1.html

    Read it to your children at night, guaranteed to help you win the custody battle.

    #nix #nixos #wireguard #linux #kernel #blogs #marmite #legalizeskyburials #foss #oss #flakes

  24. Okay, the long awaited, most anticipated, overly masturbated part two is ready for public consumption:

    https://blog.xvrqt.com/nix-wireguard-key-gen.html

    We're finally,
    almost, ready to configure Wireguard ​:hypecirno:​

    Also, I won't have to write any more shell scripts in Nix which I do not enjoy at all.

    If you give it a read please let me know! I find it encouraging, and the feedback helps me grow as a writer.

    #nix #wireguard #linux #kernel #flakes #nixox #age #agenix

  25. Any tips and tricks for using for : when the "mother flake" flake lives on a public repo & is set up to provide multiple for different machines built using:
    nixos-rebuild switch --flake .#<machine_name>
    I dug myself into a hole by copying the files from the mother flake repo to set up a new machine and the flake on my new machine has diverged & cannot be merged back into the mother flake repo because I did not *clone* it down so has no common git history

  26. 1/6
    I’ve been thinking through disaster recovery with , impermanence, and .
    A flake defines a system declaratively, but assumes storage (e.g. ZFS pools) and persisted data (e.g. /persist) already exist. Flakes don’t create storage—they only configure it. Right?

  27. https://blog.xvrqt.com/nix-wireguard.html

    Writing a new series on using Nix to configure Wireguard. It's probably overly ambitious as I have had the completed flake done for personal use for weeks now, but writing the blog means redoing it step by step in excruciating detail.

    I had to keep cutting scope for each post and now, after typing all day, I finally have... the basic option setup for it. How is writing so hard? Why would a loving god cause such agony?

    Feedback welcome, as I think part of my problem is I don't understand who my audience is so I never know what I can leave out and what I should explain further.

    #nix #nixos #linux #wireguard #kernel #flakes #foss