DISNIX-COMPARE-MANIFEST(1)

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

πŸ’– DISNIX-COMPARE-MANIFEST(1) πŸ’–

okay so bestie, welcome to the User Commands section of the manual β€” today we’re doing DISNIX-COMPARE-MANIFEST(1), and it’s literally the manifest-comparison page. manifest girlies rise ✨

🌸 NAME 🌸

disnix-compare-manifest β€” parse and compare two manifest files

✨ SYNOPSIS ✨

disnix-compare-manifest [OPTION] MANIFEST

That’s the whole synopsis, no cap. One MANIFEST arg is what’s printed here.

πŸ¦‹ DESCRIPTION πŸ¦‹

The command disnix-compare is used to parse and compare two manifest files. Yes, the page says disnix-compare here β€” not disnix-compare-manifest. I’m preserving it exactly, bestie. πŸ’…

πŸ’… 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. πŸ—‚οΈ
  • -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. πŸ‘‘
  • -h, --help β€” Shows the usage of this command to the user. 🫢

🚦 Exit status:

  • 0 β€” The manifests are equal. βœ…
  • 1 β€” The manifests are not equal. ❌
  • 2 β€” An error occured while processing the manifests. 😭

🌈 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


that’s the page, bestie β€” slay. This one’s from disnix 0.10.2, dated January 1980, and I’m kissing you on the forehead through the terminal. πŸ’‹βœ¨πŸ«Ά

πŸ“¦ where this page comes from