nethsm(1)

πŸ“¦ version 0.10.0, in arch rolling

πŸ’… nethsm(1) β€” the "nethsm" CLI, explained by your fave Unix bestie

okay so picture this: you're in the General Commands Manual section of the man pages, and you just cracked open nethsm(1). bestie, you're in the right place. this is the top-level entry point for the nethsm CLI β€” like, the front door of the whole thing. everything else lives behind a subcommand. let's get into it πŸŽ€

✨ NAME ✨

nethsm β€” the "nethsm" CLI. that's literally it, that's the whole name section. short, sweet, iconic. πŸ‘‘

🌸 SYNOPSIS 🌸

nethsm [-a|--auth-passphrase-file] [-c|--config] [-l|--label]
[-u|--user] [-h|--help] [-V|--version] <subcommands>

so yeah, you got your global flags at the front, then you tell it which <subcommands> you want. the flags live before the subcommand β€” the way that ordering matters is so real. πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

The "nethsm" CLI. that's what the manpage says, and honestly? we respect the brevity. this is the umbrella binary β€” it holds all the global options and then hands you off to whatever subcommand actually does the thing. main character energy is the subcommands, but the parent is the one driving the car. πŸš—βœ¨


πŸ’– OPTIONS πŸ’–

  • -a, --auth-passphrase-file <AUTH_PASSPHRASE_FILE> β€” the path to a file containing a passphrase for authentication.
    • the passphrase in that file must be the one for the user you chose for the command. like, no cap, they have to match.
    • this option can be provided multiple times, which is needed for commands that require multiple roles at once. with multiple passphrase files, ordering matters, because the files get assigned to the respective user provided by the "--user" option. so don't just throw them in there in any old order, bestie 😭
    • may also be specified with the NETHSM_AUTH_PASSPHRASE_FILE environment variable.
  • -c, --config <CONFIG> β€” the path to a custom configuration file.
    • if specified, the custom configuration file is used instead of the default configuration file location. basically: you're overriding the default spot. πŸ—‚οΈ
    • may also be specified with the NETHSM_CONFIG environment variable.
  • -l, --label <LABEL> β€” a label uniquely identifying a device in the configuration file.
    • must be provided if more than one device is setup in the configuration file. (read: if you've got multiple devices configured, the CLI isn't gonna guess which one you mean β€” tell it.) πŸ™ˆ
    • may also be specified with the NETHSM_LABEL environment variable.
  • -u, --user <USER> β€” a user name which is used for a command.
    • can be provided if no user name is setup in the configuration file for a device. must be provided if several user names of the same target role are setup in the configuration file for a device. iykyk β€” ambiguous config, you gotta disambiguate.
    • this option can be provided multiple times, which is needed for commands that require multiple roles at once. multiple roles = multiple users, periodt.
    • may also be specified with the NETHSM_USER environment variable.
  • -h, --help β€” print help. (see a summary with '-h') πŸ’¬
  • -V, --version β€” print version.
heads up bestie: a lot of these have environment variable twins β€” NETHSM_AUTH_PASSPHRASE_FILE, NETHSM_CONFIG, NETHSM_LABEL, NETHSM_USER. env vars are lowkey the vibe when you don't wanna retype flags every single time. ✨

πŸŽ€ SUBCOMMANDS πŸŽ€

every single one of these has its own manpage, and they're all linked below. go off, explore, the whole menu is yours 🫢

⭐ VERSION ⭐

v0.10.0

🌈 AUTHORS 🌈

David Runge <dvzrv@archlinux.org>, Wiktor Kwapisiewicz <wiktor@archlinux.org> β€” absolute legends, we stan πŸ’œ


and that's the page, bestie!! πŸŽ‰ this one's nethsm version 0.10.0, and you'll see nethsm 0.10.0 stamped in the footer of the original along with the nethsm(1) manual reference β€” so if anyone asks where you got all this, that's the receipt. now go nethsm --help something and slay πŸ’…βœ¨πŸ“

πŸ“¦ where this page comes from