DISNIX-ACTIVATE(1)

📦 version 0.10.2, in nixos 26.05, nixpkgs unstable

💅 DISNIX-ACTIVATE — bestie edition

okay so this is the manual page for disnix-activate, straight out of the disnix family of commands. pull up a chair 🎀

✨ NAME ✨

disnix-activate — activate a configuration described in a manifest. literally what it says on the tin, no cap.

🦋 SYNOPSIS 🦋

disnix-activate [OPTION] MANIFEST

🌸 DESCRIPTION 🌸

okay so picture this: the command disnix-activate activates all the services in the manifest file you hand it, on the target machines, and it does it in the right order — by traversing the inter-dependency graph of the services. it's giving graph traversal realness 👑

if there's already a configuration deployed? then this command performs an upgrade. slay.

here's the order of operations, bestie:

  1. first it deactivates all the obsolete services which are not present in the new configuration.
  2. finally it activates all the new services in the new configuration.

and during that second phase it takes inter-dependencies into account, so that no service will fail due to a broken inter-dependency closure. we do NOT do broken closures in this house 🙅‍♀️

in case of a failure, a rollback is performed: all the newly activated services are deactivated and all deactivated services are activated again. it's giving "undo undo undo" 😭

most users don't need to use this command directly, fr fr. the disnix-env command will automatically invoke this command to activate the new configuration. so unless you're being a main character about it, you can let disnix-env handle it 💖

🎀 OPTIONS 🎀

  • -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.
  • -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. most users do not want to use this option directly, but it's used by e.g. the virtualization extension to store the virtual machine profile in a separate directory.
  • --no-upgrade — by enabling this option Disnix does not store the deployment state for further use, such as upgrading.
  • --no-rollback — do not roll back if an error occurs while deactivating and activating services. (yes bestie, that means the mess stays. be so serious before you turn this on 💀)
  • --dry-run — prints the activation and deactivation steps that will be performed but does not actually execute them. vibe check mode only ✨
  • -h, --help — shows the usage of this command to the user.
  • -v, --version — shows the version of this command to the user.

🫶 Exit status 🫶

  • 0 — transition succeeded. periodt. 💅
  • 1 — transition failed, but was successfully roll backed.
  • 2 — transition failed and the rollback of the obsolete mappings failed. 😭
  • 3 — transition failed and the rollback of the new mappings failed. 💀

🌈 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

and that's the whole page, bestie 🍓 this was disnix version 0.10.2, dated January 1980 (yes, really, iconic behavior honestly 🧚). go forth and activate responsibly 💜

📦 where this page comes from