DISNIX-CLIENT(1)
π 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 asechoorprocess. π§--arguments=ARGUMENTSβ Specifies the arguments passed to the Dysnomia module, which is a string withkey=valuepairs π--container=CONTAINERβ Name of the container in which the component is managed. If omitted it will default to the same value as thetype. π«
πΈ 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
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
- nixos 26.05: disnix 0.10.2
- nixpkgs unstable: disnix 0.10.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms