BUNDLE-INIT(1)

💖 BUNDLE-INIT 💖

okay bestie, welcome to the bundle-init page — this is the bundle-init(1) situation from the General Commands Manual, and she is so much simpler than she looks 🫶

---

✨ NAME ✨

bundle-init — literally just generates a Gemfile into the current working directory, no cap 🎀

---

🌸 SYNOPSIS 🌸

bundle init [--gemspec=FILE]

---

💅 DESCRIPTION 💅

okay so here's the tea ☕ — init generates a default [Gemfile(5)][Gemfile(5)] right there in your current working directory. iconic behavior, zero effort, she just appears 💖

and here's the part that's giving main character energy: when you're adding a [Gemfile(5)][Gemfile(5)] to a gem that already has a gemspec, the --gemspec option will automatically add each dependency listed in that gemspec file into the brand-new [Gemfile(5)][Gemfile(5)] you just made. like… she read your gemspec and did the homework for you?? obsessed 😭✨

---

👑 OPTIONS 👑

• --gemspec=GEMSPEC — use the specified .gemspec to create the [Gemfile(5)][Gemfile(5)]. yes, you're telling her which gemspec to build from 💜
• --gemfile=GEMFILE — use the specified name for the gemfile instead of Gemfile. so if you're feeling quirky and want her named something else, this is your moment 🌈

---

🎀 FILES 🎀

included in the default [Gemfile(5)][Gemfile(5)] that gets generated is this line:

# frozen_string_literal: true

this is a magic comment, and it was supported for the first time in Ruby 2.3. the presence of this line results in all string literals in the file being implicitly frozen. yes bestie, it's doing a lot with a single little comment — she's efficient like that 💅✨

---

🦋 SEE ALSO 🦋

[Gemfile(5)][Gemfile(5)] — https://guides.rubygems.org/gemfile/

[Gemfile(5)]: https://guides.rubygems.org/gemfile/

---

and that's the whole page, bestie 🫶 this one's from April 2026, BUNDLE-INIT(1), and honestly? she ate 💖 go forth and generate that Gemfile ✨