sqitch...t-usage(3pm)

💖 NAME 💖

sqitch-init-usage — the Sqitch init usage statement, bestie. That's it. That's the whole thing. It's literally just the usage screen for sqitch init, no cap. ✨

---

🌸 USAGE 🌸

Here's the vibe check, fr fr — this is exactly how you call it:

sqitch init <project>
sqitch init <project> --uri <uri>

Two whole ways to do the thing. Give it a project name, or give it a project name and a URI. That's the tea. 🎀

---

✨ OPTIONS ✨

Okay so here's the full list of flags, and bestie, you're gonna want all of them:

• --uri <uri> — hooks a URI up to your project plan. Very "this project has a home" energy. 🏡
• --engine <engine> — tells it which database engine you're on. Pick your fighter. 🔥
• --top-dir <dir> — the path to the directory holding your plan and your scripts. Everything lives here, it's giving headquarters. 👑
• -f, --plan-file <file> — the path to your deployment plan file. Yes, -f is the short one, we love a shortcut. 💅
• --target <target> — the database target you're aiming at. Locked and loaded. 🎯
• --registry <registry> — your registry schema or database. Gotta keep receipts somewhere. 🧾
• --client <path> — the path to your engine's command-line client. Go find it, it's out there. 🦋
• --extension <ext> — changes the file name extension on your change scripts. Glow-up for your filenames. ⭐
• --dir <name>=<path> — the path to a named directory. Name equals path, that's the format, don't fight it. 🌈
• -s, --set <key=value> — sets a database client variable. Key equals value, iconic. 🍓

---

No warnings, no bugs, no scary caveats in this one — it's just the usage statement, so you're safe. Go off. 🫶

---

And that's a wrap, my love! This lil page is from perl v5.40.1, dated 2026-07-26, and filed under sqitch...t-usage(3pm) in the User Contributed Perl Documentation collection. Mwah. 💜