DISNIXOS-CAPTURE-MANIFEST(1)

πŸ“¦ version 0.9.4, in nixos 26.05, nixpkgs unstable

πŸ’… disnixos-capture-manifest πŸ’…

okay bestie, this is the DISNIXOS-CAPTURE-MANIFEST(1) page from the User Commands manual, and your fave command is disnixos-capture-manifest. we are literally about to capture all the ingredients for rebuilding a deployment manifest, and yes it's giving main character energy. ✨


πŸ’– NAME πŸ’–

  • disnixos-capture-manifest β€” captures all the ingredients for reconstructing a deployment manifest from the manifests of the target profiles. slay. πŸ’–

✨ SYNOPSIS ✨

disnixos-capture-manifest [OPTION] network_nix [ network2_nix ... ]

πŸ¦‹ DESCRIPTION πŸ¦‹

The command `disnixos-capture-manifests' (yes, plural-ish with a little apostrophe moment, iykyk) consults the manifests of the target Disnix profiles, retrieves their intra-dependency closures, and composes a Nix expression that can be used to reconstruct the deployment manifest on the coordinator machine. literally building the blueprint, no cap. 🌈


πŸ’… OPTIONS πŸ’…

  • -p, --profile=PROFILE β€” name of the profile in which the services are registered. Defaults to: default πŸŽ€
  • --interface=INTERFACE β€” path to executable that communicates with a Disnix interface. Defaults to `disnix-ssh-client' πŸ¦‹
  • --target-property=PROP β€” the target property of an infrastructure model, that specifies how to connect to the remote Disnix interface. (Defaults to hostname) πŸ’«
  • -m, --max-concurrent-transfers=NUM β€” maximum amount of concurrent closure transfers. Defauls to: 2 😭 (yes, "Defauls" is exactly what it says, we're keeping the typo, periodt)
  • --use-nixops β€” use NixOps instead of Disnix for infrastructure deployment πŸ‘‘
  • -h, --help β€” shows the usage of this command to the user 🫢
  • -v, --version β€” shows the version of this command to the user ⭐

🌸 ENVIRONMENT 🌸

  • DISNIX_CLIENT_INTERFACE β€” sets the client interface (which defaults to `disnix-ssh-client' β€” and yes, the closing paren is on vacation, we still love her πŸ’€
  • DISNIX_TARGET_PROPERTY β€” specifies which property in the infrastructure Nix expression specifies how to connect to the remote interface (defaults to: hostname) 🧚
  • DISNIX_PROFILE β€” sets the name of the profile that stores the manifest on the coordinator machine and the deployed services per machine on each target (Defaults to: default) πŸ’œ

Copyright Β© 2008-2022 Sander van der Burg


and that’s the tea β˜• β€” source/version: disnixos-capture-manifest (dis...; date: January 1980; manual: DISNIXOS-CAPTURE-MANIFEST(1). byeee bestie, go capture those manifests responsibly πŸ’–πŸ«Ά

πŸ“¦ where this page comes from