DISNIX-DEPLOY(1)

📦 version 0.10.2, in nixos 26.05, nixpkgs unstable

💖 DISNIX-DEPLOY 💖

okay so bestie, welcome to the disnix-deploy(1) manual page from the User Commands section ✨ — it's giving “deploy a prebuilt Disnix manifest” energy, and we are gonna go through every single crumb together, no cap. 🫶

🌸 NAME 🌸

disnix-deploy — Deploys a prebuilt Disnix manifest. periodt. 💅

✨ SYNOPSIS ✨

disnix-deploy [OPTION] MANIFEST

💅 DESCRIPTION 💅

okay so the command disnix-migrate is used to snapshot, transfer and restore the state of services that have been moved from one machine to another. yes, bestie, that's literally what the page says — I'm just the messenger 😭

Most users don't need to use this command directly. The disnix-env command will automatically invoke this command to activate the new configuration. icon behavior, honestly. 💖

🎀 OPTIONS 🎀

  • -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. full restore vibe, no upgrade. 💀
  • --no-migration — Do not migrate the state of services from one machine to another, even if they have been annotated as such. nope, staying put. 🛑
  • --no-lock — Do not attempt to acquire and release any locks. lowkey unlock mode. 🔓
  • --delete-state — Remove the obsolete state of deactivated services. bye obsolete state, we don't know her. 🗑️
  • --transfer-only — Transfers the snapshot from the target machines, but does not actually restore them. just the transfer, bestie. 📦
  • --depth-first — Snapshots components depth-first as opposed to breadth-first. This approach is more space efficient, but slower. space-saving queen but she takes her time 🐢
  • --all — Transfers all snapshot generations of the target machines, not the latest. give me the whole generation lineup, not just the newest. 🌈
  • --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. default lore is usually enough, iykyk. ✨
  • -m, --max-concurrent-transfers=NUM — Maximum amount of concurrent closure transfers. Defauls to: 2 (spelling exactly as the page says, bestie 😭)
  • -h, --help — Shows the usage of this command to the user. help girlie is here to help. 🫶

🦋 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). 🎀
  • DISNIX_DELETE_STATE — If set to 1 it automatically deletes the obsolete state after upgrading. (defaults to: 0) 🗑️
  • DYSNOMIA_STATEDIR — Specifies where the snapshots must be stored on the coordinator machine (defaults to: /var/state/dysnomia). 🗂️

Copyright © 2008-2022 Sander van der Burg

okay bestie, that's the whole page — every flag, default, env var, and copyright crumb is here. this iconic manual page is from disnix 0.10.2, dated January 1980, and the manual page header is DISNIX-DEPLOY(1). bye, slay, and may your manifests be prebuilt. 💅✨🫶

📦 where this page comes from