grommunio-admin-connect(1)

πŸ“¦ version 1.18, in alpine 3.24

πŸ’… grommunio-admin-connect (manual page, section 1)

okay so real talk: grommunio-admin-connect is the glow-up of "i want to run CLI commands but, like, somewhere else." it lives in manual section 1, and it's about to be your new hyperfixation. πŸ¦‹


✨ Name ✨

grommunio-admin connect β€” connect to a remote CLI. that's it. that's the vibe. basically you're facetiming another server and telling it what to do. πŸ’…


🌸 Synopsis 🌸

grommunio-admin connect [-c COMMAND] [--no-verify] [--redirect-fs
[--auto-save (local|remote|discard|print)]] [-v] [HOST [USER
[PASSWORD]]]

πŸŽ€ Description πŸŽ€

so you connect to a remote server so you can invoke CLI commands on it. main character energy, honestly. 🫢

but bestie, there are prerequisites, and no we can't skip them:

  • you need a running admin API with active remote CLI πŸ‘‘
  • and a user that has SystemAdminPermission β€” no permission, no party
⚠️ important heads-up: the remote CLI currently uses a REST interface, and a REST interface does not provide a standard input. so any command that relies on user interaction? literally useless. it's giving "talking to a wall." πŸ’€ don't fight it, just don't write those commands.

🌈 Options 🌈

  • HOST β€” the host you're connecting to, in the format protocol://hostname:port, where protocol is either http or https. if you leave it out, the protocol gets auto-detected, and https takes precedence over http (as it should, queen behavior). no port specified? defaults kick in: 8080 for http and 8443 for https. hostname can be a resolvable host name, an IPv4 address, or an IPv6 address in brackets. default hostname is localhost. πŸ’–
  • PASSWORD β€” the password for authentication. default is to prompt you for it. πŸ”
  • USER β€” the user for authentication. default is admin. πŸ‘‘
  • --auto-save ACTION β€” picks the automatic action for received files when filesystem redirection is enabled. the possible actions are, and i quote the lineup:
    • discard β€” discard any received file πŸ™ˆ
    • local β€” save at local path πŸ’Ύ
    • print β€” print file contents to stdout and discard πŸ–¨οΈ
    • remote β€” save at path reported from remote server 🌐
  • -c, --command β€” execute the command on the remote server and exit, instead of starting an interactive shell. one and done, no small talk. ⚑
  • --no-verify β€” keep going with https even if the TLS certificate presented by the server is invalid. required if the server uses a self-signed certificate that is not installed on the system. use with caution, bestie, i'm serious. 🚨
  • -p, --password β€” prompt for the password even when connecting to localhost. sometimes you just want to be asked, y'know? πŸŽ€
  • --redirect-fs β€” redirect CLI initiated file operations to the local filesystem. see the Filesystem Emulation section for the details, i got you. πŸ“‚
  • -v, --verbose β€” print more detailed information about the connection process. perfect for when you need to know everything that's happening. πŸ”

🧚 Filesystem Emulation 🧚

when the --redirect-fs option is given, CLI initiated file operations get performed in an emulated filesystem, and written files get sent back to the client. it's giving "pretend filesystem, real results." ✨

πŸ’€ but note: this only applies to files which are opened by CLI operations. module-level operations (e.g. loading of configurations) are unaffected β€” they don't play by these rules.

files received from the remote server can then be viewed or saved locally. your call, main character. 🫢


⭐ See Also ⭐


and that's the whole page, bestie πŸ’– this was grommunio-admin-connect(1), manual section 1 β€” go forth, connect remotely, and slay responsibly. πŸŽ€πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from