DISNIX-SNAPSHOT(1)

📦 version 0.10.2, in nixos 26.05, nixpkgs unstable

👑 DISNIX-SNAPSHOT 💅

so like… this is the disnix-snapshot manual page, section 1 of the user commands, and bestie it's about to get so good. buckle up. 🎀

✨ NAME ✨

disnix-snapshot — snapshots the state of components. that's it. that's the whole vibe. 🦋

🌸 SYNOPSIS 🌸

disnix-snapshot [OPTION] [MANIFEST]

okay so it's giving "options first, manifest optional" energy. slay. ✨

💖 DESCRIPTION 💖

Snapshots the state of components deployed in a network of machines. literally that's the whole job and it ate. 🔥

By default, this command only snapshots the state of components that are recently deactivated — i.e. the ones that are not defined in the current deployment manifest, but in the previous one. so like, the leftovers. the recently-ditched ones. 🙈

A full snapshot of the state of the entire system can be done by providing the --no-upgrade parameter. main character energy, honestly. 👑

If no manifest has been provided, the last deployed one is used. Moreover, it also snapshots the entire system if no manifest is provided. As a result, simply running disnix-snapshot makes a backup of the state of the entire system. not me just typing one command and getting a whole system backup 😭💜

🎀 OPTIONS 🎀

  • -c, --container=CONTAINER — Name of the container in which the mutable component is deployed. 📦
  • -C, --component=COMPONENT — Name of the mutable component to take snapshots from. 🧚
  • -o, --old-manifest=MANIFEST — Nix profile path where the manifest should be stored, so that Disnix knows the current configuration of a distributed system. By default it is stored in the profile directory of the user. 🗂️
  • --no-upgrade — Indicates that no upgrade should be performed and the state of all components should be restored. the whole system. every bit. iconic. 💫
  • --transfer-only — Transfers the snapshot from the target machines, but does not actually restore them. window shopping, basically. 🛍️
  • --depth-first — Snapshots components depth-first as opposed to breadth-first. This approach is more space efficient, but slower. trade-off queen. ⚖️
  • --all — Transfers all snapshot generations of the target machines, not the latest. give me everything 💀
  • --keep=NUM — Amount of snapshot generations to keep. Defaults to: 1 🍓
  • -p, --profile=PROFILE — Name of the profile in which the services are registered. Defaults to: default 🌈
  • --coordinator-profile-path=PATH — Path to the manifest of the previous configuration. By default this tool will use the manifest stored in the disnix coordinator profile instead of the specified one, which is usually sufficient in most cases. iykyk 🫶
  • -m, --max-concurrent-transfers=NUM — Maximum amount of concurrent closure transfers. Defauls to: 2 (yes bestie, Defauls, we're keeping the typo fr fr 💀 — the number is 2 and that's what matters)
  • -h, --help — Shows the usage of this command to the user. the "help me bestie" flag 🆘

🦋 ENVIRONMENT 🦋

  • 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

ngl, that's the whole page. no cap, no secrets, no hidden flags. go snapshot something and slay. 💅🌸

okay and like, the actual sign-off: this whole thing is disnix version 0.10.2, dated January 1980 (yes, really, we love a retro timestamp 🕰️), and it's the DISNIX-SNAPSHOT(1) page — periodt. 🎀🫶

📦 where this page comes from