feat: configurable `pod` command / try local `bundle exec pod`

Feature Request

Description

Some projects may chose to not install pod globally, but locally via bundle. In this case, pod is normally not in the $PATH. However, it would be accessible via bundle exec pod.

Because cap expects pod to be accessible from the $PATH, any command using pod would fail with that setup.

Currently we work around this in our project by generating a binstub for pod (bundle binstubs cocoapods) and adding it to the $PATH using an .envrc file like this:

# Add the gem binstubs directory to `PATH`.
export PATH="$PWD/bin:$PATH"

Platform(s)

macOS / iOS

Preferred Solution

Not entirely sure.

It would be nice, if the command for pod could be configured or alternatively the path to the bin could be configured explicitly. Both solutions could be supported simultaneously. I would not put this in the capacitor.config.json, but rather add a capacitor key to the package.json:

{
  "capacitor": {
    "pod": "bundle exec pod"
    // or alternatively:
    "pod": "./bin/pod"
  }
}

[buschtoens]

Thanks for mentioning. That’d be fine as well though. If users for some reason cannot use binstubs, they could create an executable (chmod +x) shell script instead:

#!/usr/bin/env sh
bundle exec pod $@

export CAPACITOR_COCOAPODS_PATH="./bin/custom-pod"

[buschtoens]

We use a monorepo setup that looks like this: (irrelevant files & directories omitted)

.
├── .bundle
│  └── config
├── bin
|  |   # These binstubs were generated via
|  |   # `bundle binstubs cocoapods`
|  |   # and are checked into the repo.
│  ├── pod
│  └── sandbox-pod
├── gems
│  └── ruby/
|      # Contains the `Gemfile` dependencies. Created by
|      # `bundle install`
|      # Not checked into the repository.
|      # See further down this comment for the contents.
├── packages
│  ├── capacitor-app/
│  ...
│  ├── plugin.auth/
│  ├── plugin.pdf/
│  └── scripts/
├── .envrc
├── .gitignore
├── .ruby-version
├── Brewfile
├── Gemfile
├── Gemfile.lock
├── lerna.json
├── package.json
├── README.md
└── yarn.lock

For our tool chain version management we have (among others) these entries in our Brewfile:

brew "direnv"
brew "volta"
brew "rbenv"
brew "openjdk@11"

And this .envrc:

# Add the gem binstubs directory and the JDK@11 to the `PATH`.
export PATH="$(dirname "$0")/bin:$(brew --prefix openjdk@11)/bin:$PATH"

And this .bundle/config:

---
BUNDLE_PATH: "./gems"
BUNDLE_FROZEN: "true"

And here’s the contents created by bundle install:

./gems/ruby/2.7.0
├── bin
│  ├── bin-proxy
│  ├── dotenv
│  ├── fastlane
│  ├── fuzzy_match
│  ├── generate-api
│  ├── httpclient
│  ├── pod
│  ├── rake
│  ├── rougify
│  ├── sandbox-pod
│  ├── terminal-notifier
│  ├── ww
│  ├── xcodeproj
│  ├── xcpretty
│  └── xcpretty-travis-formatter
├── build_info
├── cache
│  ├── activesupport-4.2.11.3.gem
│  ...
│  └── xcpretty-travis-formatter-1.0.0.gem
├── doc
├── extensions
│  └── x86_64-darwin-19
├── gems
│  ├── activesupport-4.2.11.3
│  ...
│  └── xcpretty-travis-formatter-1.0.0
└── specifications
   ├── activesupport-4.2.11.3.gemspec
   ...
   └── xcpretty-travis-formatter-1.0.0.gemspec

Our Gemfile looks like this:

source "https://rubygems.org"

gem "fastlane"
gem "cocoapods"
# ...

fastlane_plugins_path = File.join(
  File.dirname(__FILE__),
  'packages',
  'capacitor-app',
  'ios',
  'App',
  'fastlane',
  'Pluginfile'
)
eval_gemfile(fastlane_plugins_path) if File.exist?(fastlane_plugins_path)

And the Pluginfile:

# Autogenerated by fastlane
#
# Ensure this file is checked in to source control!

gem 'fastlane-plugin-sentry'