YTE(1)

💖 YTE(1) — the yte page, but make it make sense 💖

okay bestie, sit down, hydrate, because we're about to process some YAML together and it's gonna be so clean. this is the manual for yte, a User Command, and yes i'm about to explain every single flag because you deserve the full picture, not a summary. 🫶

---

✨ NAME ✨

yte — Process a YAML file given at STDIN with YTE, and print the result to STDOUT

like. that's the whole job. yaml goes in, yaml comes out. it's giving pipeline main character energy. 👑

---

🎀 SYNOPSIS 🎀

yte [-h] [--template TEMPLATE] [--output OUTPUT] [--require-use-yte]
[--variable-file VARIABLE_FILE] [--variables [VARIABLES ...]]
[--version]

copy that exactly, don't get cute with it, i am cute enough for both of us. 💅

---

🌸 DESCRIPTION 🌸

Process a YAML file given at STDIN with YTE, and print the result to STDOUT.

that's it. that's the vibe. you pipe yaml in, YTE does its thing, the result lands on STDOUT. chef's kiss, no notes. 🍓

⚠️ not me warning you but actually warning you: if nothing is provided at STDIN, this will wait forever. like, forever forever. it will just sit there. staring. respectfully, don't do that to yourself. feed it something or ctrl-c. 😭

---

🌈 OPTIONS 🌈

• -h, --help — Show a help message and exit. the classic. the escape hatch. when in doubt, ask for help, bestie. ✨
• --template TEMPLATE — Path to the template file. and here's the lil twist: if you pass -, it reads from STDIN instead. so - = "stdin, surprise me." 🦋
• --output OUTPUT — Path to the output file. same deal as above: if you pass -, it writes to STDOUT. iconic symmetry, honestly. 💜
• -r, --require-use-yte — Require that the document contains a

__use_yte__: true

statement at the top level. if that statement is not present, or it's false, it returns the document unprocessed — with one exception: it still removes the

__use_yte__: false

statement if it's present. so like, it's not fully hands-off, it just quietly tidies that one line away. lowkey thoughtful of it. 🙈

• --variable-file VARIABLE_FILE — Path to a file containing a map of variables for the template (.json or .yaml format). heads up though: values given here are overwritten by values with the same names in the --variables option. so --variables is the loud friend who talks over the file. that's just the hierarchy. 🎀
• --variables [VARIABLES ...] — Space separated list of variables to use in the template, given as name=value pairs. so like, name=value name2=value2, one long space-separated lil family. 💖
• --version — Print version and exit. short, sweet, informative. periodt. ⭐

---

🧚 a lil sign-off 🧚

this page is from November 2025, and it lives in the User Commands section of the manual as YTE(1). that's the whole footer, bestie — no cap, that's genuinely all of it. now go pipe something into STDIN before it waits forever. mwah. 💅💖🌸