ortie(1)

📦 version 2.1.0, in nixpkgs unstable

💅 ortie(1) — like, the manual page, bestie

okay so you've stumbled into the ortie(1) page from the General Commands Manual and honestly? you're gonna be fine. this is the CLI to manage OAuth 2.0 tokens, and I'm gonna walk you through every single flag like we're sitting on facetime. no cap, nothing skipped. 🫶

✨ NAME ✨

ortie — CLI to manage OAuth 2.0 tokens. that's it. that's the whole vibe. 🎀

🌸 SYNOPSIS 🌸

ortie [-c|--config] [-a|--account] [--json] [--log-level] [--log-file]
[-h|--help] [-V|--version] [subcommands]

like, that's the shape of it. flags in, subcommands in, ortie does the thing. 💫

🦋 DESCRIPTION 🦋

CLI to manage OAuth 2.0 tokens.

yes bestie, that's genuinely what the manpage says and honestly it's all you need. tokens? managed. OAuth 2.0? handled. moving on. ✨

✨ OPTIONS ✨

  • -c, --config <PATH> — override the default configuration file path. the paths you give get shell-expanded then canonicalized (if applicable). and here's the cute part: other paths get merged with the first one, which lets you keep your public config separate from your private one(s). separation is self-care, fr fr. 🍓
  • -a, --account <NAME> — override the default account. an account name corresponds to an entry in the table at the root level of your TOML configuration file. iykyk. 💜
  • --json — enable JSON output. when set, command output (data or errors) is displayed as a JSON string. yes, even the errors get the JSON treatment. slay. 🔥
  • --log-level <LEVEL> — filter log output by level. when it's omitted, the RUST_LOG environment variable is consulted instead (it supports per-target filters — go read the env_logger documentation for that). when this flag is present, it overrides RUST_LOG entirely. no sharing, periodt. 💅

possible values:

  • off: no logging
  • error: errors only
  • warn: warnings and errors
  • info: informational messages and above
  • debug: debug messages and above
  • trace: trace messages and above (most verbose — buckle up 😭)
  • --log-file <PATH> — append log output to the given file instead of stderr. this is so useful when interactive prompts (which always write to stderr, always always) would otherwise get intermixed with log lines. the file is opened in append mode and created if it doesn't exist. tidy. 🧚
  • -h, --help — print help (see a summary with -h). yes it tells you how to ask for less help. iconic. 👑
  • -V, --version — print version. 📌

🌈 SUBCOMMANDS 🌈

  • ortie-auth(1) — get a fresh access token by running the account's OAuth grant. new token, who dis. 🔑
  • ortie-token(1) — display and refresh an existing OAuth 2.0 access token.
  • ortie-repl(1) — start a persistent REPL session for one account. main character energy only. ✨
  • ortie-manuals(1) — generate manual pages to the given directory.
  • ortie-completions(1) — generate completion script for the give shell(s) to the given directory. (yes, "give" — that's exactly what the original says, I'm not fixing it, it's canon now 💀)
  • ortie-help(1) — print this message or the help of the given subcommand(s).

⭐ VERSION ⭐

vv2.1.0 +rustls-ring build: macos  aarch64 git: unknown, rev unknown

yeah, vv2.1.0. two v's. don't ask, just accept. it's giving unhinged build metadata and I respect it. 🌈

💖 AUTHORS 💖

Clément DOUIN (soywod) <pimalaya.org@posteo.net> — thank you for the tokens, king. 🫶

ngl that's the whole page. every flag, every value, every subcommand, every path rule — all here, bestie. nothing left behind. 💅

so like… that's ortie 💜 this was the ortie 2.1.0 manual page, and the footer said ortie 2.1.0 and honestly there was no date on it so I can't give you one, sorry 😭 anyway go manage your tokens, you're gonna ate. 🎀

📦 where this page comes from