DISNIXOS-MANIFEST(1)

📦 version 0.9.4, in nixos 26.05, nixpkgs unstable

💖 NAME 💖

okay so bestie, welcome to disnixos-manifest — the lil tool that generates a manifest file from your DisnixOS expressions. that's it, that's the whole vibe ✨

🌸 SYNOPSIS 🌸

disnixos-manifest -s services_nix -n network_nix [ -n network2_nix ... ]
-d distribution_nix [OPTION]
disnixos-manifest -P packages_nix -n network_nix [ -n network2_nix ... ]
[OPTION]
disnixos-manifest -n network_nix [ -n network2_nix ... ] [OPTION]

three whole moods, pick whichever one your setup needs 🫶

🦋 DESCRIPTION 🦋

so the command disnixos-manifest generates a manifest file out of a service, network and distribution Nix expression. what's it for? distributing services to machines in the network, and activating those services on the target machines in the right order. slay, ordering matters 💅

and here's the tea: because the manifest file contains Nix store paths of every service, running this command has a side effect — all the services that have to be activated get automatically built from source and dropped into the Nix store of the coordinator machine. no cap, it's doing a whole lot behind your back 😭

ngl, most users and developers do not need to use this command directly. the command disnixos-env handles manifest generation automatically for you. this one is mostly for debugging purposes, or for when you wanna do certain tasks manually. main character energy only 🔥

✨ OPTIONS ✨

  • -s, --services=services_nix — the Services Nix expression, which describes, like, all the components of your distributed system 💖
  • -n, --network=network_nix — the Network Nix expression, which declares a NixOS configuration for every machine in the network 🌈
  • -d, --distribution=distribution_nix — the Distribution Nix expression, the one that maps services to machines in the network 🎀
  • -P, --packages=packages_nix — the Packages Nix expression, which specifies the packages that should be deployed in a Nix profile mapped to each machine in the network 🍓
  • --target-property=PROP — the target property of an infrastructure model, which specifies how to connect to the remote Disnix interface. (defaults to hostname, iykyk) 👑
  • --interface=INTERFACE — path to the executable that communicates with a Disnix interface. defaults to: disnix-ssh-client 🧚
  • --deploy-state — tells it whether to globally deploy state. heads up: it's disabled by default 🙈
  • --extra-params=PARAMS — a string with an attribute set in the Nix expression language, propagating extra parameters to the input models 💜
  • --no-out-link — do not create a result symlink. no lil symlink for you 😌
  • --show-trace — shows a trace of the output. for when you simply must know 🔍
  • --vm — configures a manifest used for the NixOS test driver 🦋
  • --use-nixops — use NixOps instead of Disnix's deployment facilities ✨
  • --disable-disnix — do not enable the Disnix service on the target machines by default 💅
  • -h, --help — shows the usage of this command to the user. bestie behaviour fr 🫶
  • -v, --version — shows the version of this command to the user ⭐

🎀 ENVIRONMENT 🎀

  • DISNIX_CLIENT_INTERFACE — sets the client interface. (defaults to: disnix-ssh-client) 💖
  • DISNIX_TARGET_PROPERTY — sets the target property of an infrastructure model, which specifies how to connect to the remote Disnix interface. (defaults to: hostname) 🌸
  • DISNIX_DEPLOY_STATE — if it's set to 1, it also deploys the state of all components. (defaults to: 0) 🔥
  • DISNIXOS_USE_NIXOPS — when set to 1, it says NixOps is being used to take care of the infrastructure deployment — so it properly interprets NixOps configurations and uses NixOps tooling instead of Disnix's deployment facilities. lowkey important 👀

Copyright © 2008-2022 Sander van der Burg 💜

and that's the whole page bestie!! disnixos-manifest, from disnixos 0...., dated January 1980 — iconic, timeless, a lil retro 🎀💀 go forth and generate those manifests ✨🦋
📦 where this page comes from