DISNIX-MIGRATE(1)

📦 version 0.10.2, in nixos 26.05, nixpkgs unstable

💅 DISNIX-MIGRATE(1) — the group-chat edition

okay so bestie, welcome to disnix-migrate, a User Commands girly from the disnix family 🎀 she's the one who handles the glow-up when your services move houses.

✨ NAME ✨

disnix-migrate — literally migrates state from services that have been moved from one machine to another 🦋

🌸 SYNOPSIS 🌸

disnix-migrate [OPTION] MANIFEST

💖 DESCRIPTION 💖

so the command disnix-migrate is the one that snapshots, transfers and restores the state of services that have been moved from one machine to another. it's giving relocation era 🧳✨

ngl, most users don't need to use this command directly — and that's not a read, it's a compliment to automation. the disnix-env command will automatically invoke this command to activate the new configuration. she's the backstage main character, you're just here for the show 💅

🫶 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 🙈
  • --delete-state — remove the obsolete state of deactivated services 🗑️
  • --transfer-only — transfers the snapshot from the target machines, but does not actually restore them (so like, the luggage arrives but nobody unpacks 💀)
  • --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 👯‍♀️
  • --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. defaults to: 2 (the manpage spells it "Defauls", and honestly? iconic. we stan a typo 😭)
  • -h, --help — shows the usage of this command to the user 🫶

🌈 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

fr fr bestie, that's the whole page — no gatekeeping, no skipped options, every flag accounted for 💜

mwah, that's a wrap 🍓 this little icon was brought to you by disnix 0.10.2, dated January 1980 (yes, the year is a vibe, don't question her) 💅✨

📦 where this page comes from