fastlane/docs

Explain why running `bundle exec fastlane some_command` is faster than `fastlane some_command`

bartekpacia opened this issue · 3 comments

bartekpacia commented

I don't know why it's recommended and I haven't found a rationale for this anywhere.

rogerluan commented

Hi @bartekpacia 👋

I don't know about being faster 🤔 but here are a few reasons to use Bundler instead of using your machine's native Ruby gem installations, check this out: https://12factor.net/dependencies

And if you use fastlane for iOS, here's the same content tailored for iOS developers: https://ios-factor.com/dependencies

I strongly recommend checking out all the factors in https://ios-factor.com as guidelines for building scalable iOS applications 😊

But also, from bundler.io:

Bundler provides a consistent environment for Ruby projects by tracking and installing the exact gems and versions that are needed.

Bundler is an exit from dependency hell, and ensures that the gems you need are present in development, staging, and production.

I hope this helps!

bartekpacia commented

Thanks for your input @rogerluan :)

  • ❤️1
bartekpacia commented

I hope somebody, someday, will solve this mystery. It really does say "faster":

$ fastlane                                                                                                                                                                                                 exit 1
[✔] 🚀
[17:33:59]: fastlane detected a Gemfile in the current directory
[17:33:59]: However, it seems like you didn't use `bundle exec`
[17:33:59]: To launch fastlane faster, please use
[17:33:59]:
[17:33:59]: $ bundle exec fastlane
[17:33:59]:
[17:33:59]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile