DISNIX-BACKDOOR-CLIENT(1)

🎀 DISNIX-BACKDOOR-CLIENT(1) — disnix-backdoor-client manual from User Commands, bestie 🎀

🌸 NAME 🌸

disnix-backdoor-client — provides access to the disnix-service through a socket with public access. That’s the name-section vibe, and it ate. 💅

✨ SYNOPSIS ✨

Here’s the exact shape, no cap:

disnix-backdoor-client --target socat_address operation [OPTION] [paths]

🦋 DESCRIPTION 🦋

Okay so disnix-backdoor-client gives you remote access to a disnix-service instance running on a machine in the network by using an insecure socket with public access. Yes, bestie, insecure is literally in the original 😭. This tool is designed for use with disnixos-vm-env to automatically deploy a system in a network of virtual machines.

In most cases this command is not used directly. Instead, it’s used by specifying the --interface option for a Disnix command-line utility (such as disnix-env) or by setting the DISNIX_CLIENT_INTERFACE environment variable. By using one of those properties, the Disnix tools will use the given interface instead of the standard disnix-client, which only provides loopback access. Iconic indirection, honestly. 🫶

⚠️ The page says insecure socket with public access, so let’s not pretend that’s a security flex. It’s the whole backdoor-client vibe, periodt.

---

💅 OPTIONS 💅

Pick your operation, then add the options that match. Everything below is exactly what the page says — I’m just adding sparkle. ✨

🔥 Operations:

• --import — Imports a given closure into the Nix store of the target machine. Optionally, it transfers the closure from this machine to the target machine. 🎀
• --export — Exports the closure of a given Nix store path of the target machine into a file, and optionally downloads it. 🦋
• --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 only containing 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 (intra-dependencies) 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 to 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 hostname and optional port number of the SSH server used to connect to the target machine. 🌈

🎁 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 be transferred from the remote machine if needed. 🦋

🧸 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_REMOTE_CLIENT — Name of the remote executable to run to execute a deployment activity (defaults to: disnix-run-activity). 🫶
• 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). 💖
• DYSNOMIA_STATEDIR — Specifies where the snapshots must be stored on the coordinator machine (defaults to: /var/state/dysnomia). 🌸

👑 COPYRIGHT 👑

Copyright © 2008-2022 Sander van der Burg

---

💖 And that’s the whole manual, bestie. The footer’s source/version is disnix..., dated January 1980, for DISNIX-BACKDOOR-CLIENT(1). Bye and slay responsibly! 💖