COBRA-INIT(1)

💖 COBRA-INIT 💖

okay so bestie, welcome to cobra-init</c> — it's a page from the Cobra Manual and it's literally about spinning up a whole new Cobra application from scratch. no cap. 🐍✨

---

🌸 NAME 🌸

cobra-init — Initialize a Cobra Application 🎀

---

✨ SYNOPSIS ✨

cobra init [OPTIONS]

that's it. that's the whole vibe. 🫶

---

🦋 DESCRIPTION 🦋

so cobra init (cobra init, yes the same thing, they're twins) creates a brand new application for u — complete with a license and the whole appropriate structure for a Cobra-based CLI application. it's giving scaffolding. it's giving "i got u bestie". 💅

here's the tea on where ur new baby app ends up:

• 🍓 if a name is provided, it will be created in the current directory;
• 🍓 if no name is provided, the current directory will be assumed;
• 🍓 if a relative path is provided, it will be created inside $GOPATH (e.g. github.com/spf13/hugo);
• 🍓 if an absolute path is provided, it will be created;
• 🍓 if the directory already exists but is empty, it will be used.

💀 ok important one: Init will not use an existing directory with contents. like, at all. don't even try it. it said no. 🙈

---

👑 OPTIONS INHERITED FROM PARENT COMMANDS 👑

these aren't even cobra-init's own flags, they're inherited from the parent commands, but they still ate and u still need them:

• -a, --author="YOUR NAME" — author name for copyright attribution ✍️ (yes, put ur actual name in there, main character)
• --config="" — config file, and the default is $HOME/.cobra.yaml 🗂️
• -l, --license="" — name of license for the project, and you can provide licensetext in config 📜
• -b, --projectbase="" — base project directory, e.g. github.com/spf13/ 🏗️
• --viper[=true] — use Viper for configuration 🐍✨

---

🌈 SEE ALSO 🌈

• cobra(1)

---

github.com/spf13/cobra · Dec 2015

okay that's the whole page bestie, go forth and cobra init something iconic. periodt. 💖🦋✨👑