DISNIX-CLIENT(1)

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

πŸ’… NAME

okay so disnix-client β€” it's the tool that gives you access to the disnix-service through the D-Bus system bus or session bus. bestie, that's literally the whole thing ✨


πŸŽ€ SYNOPSIS

disnix-client [OPTION] operation

πŸ¦‹ DESCRIPTION

So disnix-client is your lil handshake with a disnix-service instance that's running on the same machine β€” it does that by connecting to the D-Bus system bus or session bus. no cap, that's it πŸ’…

ngl, in most cases this tool is only needed for debugging purposes, because it literally only speaks the D-Bus protocol and it cannot connect to a remote machine. like, it's not built for that, periodt.

A way more useful client for production environments is disnix-ssh-client β€” that's the one you want when things get real 🫢


✨ OPTIONS ✨

🌸 Operations:

  • --import β€” Imports a given closure into the Nix store of the target machine πŸ“¦
  • --export β€” Exports the closure of a given Nix store path of the target machine into a file πŸ’Ύ
  • --print-invalid β€” Prints all the paths that are not valid in the Nix store of the target machine πŸ™ˆ
  • -r, --realise β€” Realises the given store derivation on the target machine πŸ”₯
  • --set β€” Creates a Disnix profile containing only the given derivation on the target machine πŸŽ€
  • -q, --query-installed β€” Queries all the installed services on the given target machine πŸ”
  • --query-requisites β€” Queries all the requisites (the intra-dependencies, iykyk) of the given services on the target machine 🧚
  • --collect-garbage β€” Collects garbage on the given target machine πŸ—‘οΈ
  • --activate β€” Activates the given service on the target machine ⚑
  • --deactivate β€” Deactivates the given service on the target machine πŸ’€
  • --lock β€” Acquires a lock on a Disnix profile of the target machine πŸ”’
  • --unlock β€” Release the lock on a Disnix profile of the target machine πŸ”“
  • --snapshot β€” Snapshots the logical state of a component on the given target machine πŸ“Έ
  • --restore β€” Restores the logical state of a component on the given target machine βͺ
  • --delete-state β€” Deletes the state of a component on the given machine πŸ’€
  • --query-all-snapshots β€” Queries all available snapshots of a component on the given target machine 🌈
  • --query-latest-snapshot β€” Queries the latest snapshot of a component on the given target machine ⭐
  • --print-missing-snapshots β€” Prints the paths of all snapshots not present on the given target machine πŸ«₯
  • --import-snapshots β€” Imports the specified snapshots into the remote snapshot store πŸ“₯
  • --export-snapshots β€” Exports the specified snapshot to the local snapshot store πŸ“€
  • --resolve-snapshots β€” Converts the relative paths to the snapshots into absolute paths 🧭
  • --clean-snapshots β€” Removes older snapshots from the snapshot store 🧹
  • --capture-config β€” Captures the configuration of the machine from the Dysnomia container properties in a Nix expression πŸ“
  • --help β€” Shows the usage of this command to the user πŸ’–
  • --version β€” Shows the version of this command to the user πŸ‘‘

🌟 General options:

  • -t, --target=TARGET β€” Specifies the target to connect to. ⚠️ heads up: this property is ignored by this client because it only supports loopback connections. (yes bestie, it's a whole vibe check it just doesn't attend πŸ™ˆ)
  • --session-bus β€” Connects to the session bus instead of the system bus. This is useful for testing/debugging purposes πŸ§ͺ

πŸ“ Import/Export/Import snapshots/Export snapshots options:

  • --localfile β€” Specifies that the given paths are stored locally and must be transferred to the remote machine if needed 🏠
  • --remotefile β€” Specifies that the given paths are stored remotely and must transferred from the remote machine if needed 🌐

🐚 Shell options:

  • --command=COMMAND β€” Commands to execute in the shell session ⌨️

πŸ’œ Set/Query installed/Lock/Unlock options:

  • -p, --profile=PROFILE β€” Name of the Disnix profile. Defaults to: default 🎯

πŸ—‘οΈ Collect garbage options:

  • -d, --delete-old β€” Indicates whether all older generations of Nix profiles must be removed as well 🧼

⚑ Activation/Deactivation/Snapshot/Restore/Delete state options:

  • --type=TYPE β€” Specifies the activation module that should be used, such as echo or process. πŸ”§
  • --arguments=ARGUMENTS β€” Specifies the arguments passed to the Dysnomia module, which is a string with key=value pairs πŸ“Ž
  • --container=CONTAINER β€” Name of the container in which the component is managed. If omitted it will default to the same value as the type. πŸ«™

πŸ“Έ Query all snapshots/Query latest snapshot options:

  • -C, --container=CONTAINER β€” Name of the container in which the component is managed πŸ«™
  • -c, --component=COMPONENT β€” Name of the component hosted in a container 🧩

🧹 Clean snapshots options:

  • --keep=NUM β€” Amount of snapshot generations to keep. Defaults to: 1 πŸ”’
  • -C, --container=CONTAINER β€” Name of the container to filter on πŸ«™
  • -c, --component=COMPONENT β€” Name of the component to filter on 🧩

🌈 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 0.10.2, dated January 1980 β€” yeah, the date is iconic and a little unhinged, we don't question it πŸ’…βœ¨

πŸ“¦ where this page comes from