sqitch...e-usage(3pm)

✨ sqitch-engine-usage 💅

okay so this is the sqitch-engine-usage page, from section 3pm of the manual — yes bestie, it's a Perl thing 🫶 it's literally the usage statement for the Sqitch engine commands, and it's short, sweet, and honestly kind of iconic.

---

🌸 Name

sqitch-engine-usage — Sqitch engine usage statement 🌈

---

🎀 Usage

here's the whole vibe, every single line, no cap:

sqitch engine
sqitch engine [-v | --verbose]
sqitch engine add <name> [engine-options]
sqitch engine alter <name> [engine-options]
sqitch engine remove <name>
sqitch engine show <name>

like… run it with no args, or get verbose, or add / alter / remove / show an engine by name and optionally pass it some engine-options. the way it just does that 😌

---

💖 Options

one bullet per flag, all of them, because we do not skip details in this house ✋

• -v, --verbose — be verbose 💬 and heads up: it must be placed before an action, like it's gotta walk in first, main character energy only 👑
• --target <target> — the database target 🎯
• --registry <registry> — the registry schema or database 📚
• --client <path> — path to the engine command-line client 🖥️
• -f --plan-file <file> — path to the deployment plan file 🗂️
• --top-dir <dir> — path to the directory with plan and scripts 📁
• --extension <ext> — change script file name extension 🔤
• --dir <name>=<path> — path to a named directory 🗺️
• -s --set <key=value> — set a database client variable 🍓

---

fr fr, be careful with -v — if you drop it in after an action instead of before, it is not gonna do the thing. put it first. periodt. 💀

---

that's the whole page bestie, every option accounted for, nothing skipped, we ate and left no crumbs 💅🧚

this gem came to you via sqitch...e-usage in the 3pm manual, shipped with perl v5.40.1, dated 2026-07-26 ⭐ bye ily 🫶🎀