➜ pod --help
Usage:
$ pod COMMAND
CocoaPods, the Cocoa library package manager.
Commands:
+ cache Manipulate the CocoaPods cache
+ deintegrate Deintegrate CocoaPods from your project
+ env Display pod environment
+ init Generate a Podfile for the current directory
+ install Install project dependencies according to versions from a
Podfile.lock
+ ipc Inter-process communication
+ lib Develop pods
+ list List pods
+ outdated Show outdated project dependencies
+ plugins Show available CocoaPods plugins
+ repo Manage spec-repositories
+ search Search for pods
+ setup Setup the CocoaPods environment
+ spec Manage pod specs
+ trunk Interact with the CocoaPods API (e.g. publishing new specs)
+ try Try a Pod!
+ update Update outdated project dependencies and create new Podfile.lock
Options:
--silent Show nothing
--version Show the version of the tool
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod cache --help
Usage:
$ pod cache COMMAND
Manipulate the download cache for pods, like printing the cache content or
cleaning the pods cache.
Commands:
+ clean Remove the cache for pods
+ list List the paths of pod caches for each known pod
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod cache clean --help
Usage:
$ pod cache clean [NAME]
Remove the cache for a given pod, or clear the cache completely.
If there is multiple cache for various versions of the requested pod, you will
be asked which one to clean. Use `--all` to clean them all.
If you don't give a pod `NAME`, you need to specify the `--all` flag (this is to
avoid cleaning all the cache by mistake).
Options:
--all Remove all the cached pods without asking
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod cache list --help
Usage:
$ pod cache list [NAME]
Shows the content of the pods cache as a YAML tree output, organized by pod. If
`NAME` is given, only the caches for that pod will be included in the output.
Options:
--short Only print the path relative to the cache root
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod deintegrate --help
Usage:
$ pod deintegrate [XCODE_PROJECT]
Deintegrate your project from CocoaPods. Removing all traces of CocoaPods from
your Xcode project.
If no xcodeproj is specified, then a search for an Xcode project will be made in
the current directory.
Options:
--project-directory=/project/dir/ The path to the root of the project directory
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod env --help
Usage:
$ pod env
Display pod environment.
Options:
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod init --help
Usage:
$ pod init XCODEPROJ
Creates a Podfile for the current directory if none currently exists. If an
`XCODEPROJ` project file is specified or if there is only a single project file
in the current directory, targets will be automatically generated based on
targets defined in the project.
It is possible to specify a list of dependencies which will be used by the
template in the `Podfile.default` (normal targets) `Podfile.test` (test targets)
files which should be stored in the `~/.cocoapods/templates` folder.
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod install --help
Usage:
$ pod install
Downloads all dependencies defined in `Podfile` and creates an Xcode Pods
library project in `./Pods`.
The Xcode project file should be specified in your `Podfile` like this:
project 'path/to/XcodeProject.xcodeproj'
If no project is specified, then a search for an Xcode project will be made. If
more than one Xcode project is found, the command will raise an error.
This will configure the project to reference the Pods static library, add a
build configuration file, and add a post build script to copy Pod resources.
This may return one of several error codes if it encounters problems. * `1`
Generic error code * `31` Spec not found (i.e out-of-date source repos, mistyped
Pod name etc...)
Options:
--repo-update Force running `pod repo update` before install
--project-directory=/project/dir/ The path to the root of the project directory
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod ipc --help
Usage:
$ pod ipc COMMAND
Inter-process communication
Commands:
+ list Lists the specifications known to CocoaPods
+ podfile Converts a Podfile to YAML
+ podfile-json Converts a Podfile to JSON
+ repl The repl listens to commands on standard input
+ spec Converts a podspec to JSON
+ update-search-index Updates the search index
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod ipc list --help
Usage:
$ pod ipc list
Prints to STDOUT a YAML dictionary where the keys are the name of the
specifications and each corresponding value is a dictionary with the following
keys: - defined_in_file - version - authors - summary - description - platforms
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod ipc podfile --help
Usage:
$ pod ipc podfile PATH
Converts a Podfile to YAML and prints it to STDOUT.
Options:
--project-directory=/project/dir/ The path to the root of the project directory
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod ipc podfile-json --help
Usage:
$ pod ipc podfile-json PATH
Converts a Podfile to JSON and prints it to STDOUT.
Options:
--project-directory=/project/dir/ The path to the root of the project directory
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod ipc repl --help
Usage:
$ pod ipc repl
The repl listens to commands on standard input and prints their result to
standard output. It accepts all the other ipc subcommands. The repl will signal
the end of output with the the ASCII CR+LF `\n\r`.
Options:
--project-directory=/project/dir/ The path to the root of the project directory
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod ipc spec --help
Usage:
$ pod ipc spec PATH
Converts a podspec to JSON and prints it to STDOUT.
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod ipc update-search-index --help
Usage:
$ pod ipc update-search-index
Updates the search index and prints its path to standard output. The search
index is a YAML encoded dictionary where the keys are the names of the Pods and
the values are a dictionary containing the following information: - version -
summary - description - authors
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod lib --help
Usage:
$ pod lib COMMAND
Develop pods
Commands:
+ create Creates a new Pod
+ lint Validates a Pod
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod lib create --help
[!] A name for the Pod is required.
Usage:
$ pod lib create NAME
Creates a scaffold for the development of a new Pod named `NAME` according
to the CocoaPods best practices. If a `TEMPLATE_URL`, pointing to a git
repo containing a compatible template, is specified, it will be used in
place of the default one.
Options:
--template-url=URL The URL of the git repo containing a compatible
template
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod lib lint --help
Usage:
$ pod lib lint
Validates the Pod using the files in the working directory.
Options:
--quick Lint skips checks that
would require to download
and build the spec
--allow-warnings Lint validates even if
warnings are present
--subspec=NAME Lint validates only the
given subspec
--no-subspecs Lint skips validation of
subspecs
--no-clean Lint leaves the build
directory intact for
inspection
--fail-fast Lint stops on the first
failing platform or
subspec
--use-libraries Lint uses static libraries
to install the spec
--sources=https://github.com/artsy/Specs,master The sources from which to
pull dependent pods
(defaults to
https://github.com/CocoaPods/Specs.git).
Multiple sources must be
comma-delimited.
--private Lint skips checks that
apply only to public specs
--swift-version=VERSION The SWIFT_VERSION that
should be used to lint the
spec. This takes
precedence over a
.swift-version file.
--skip-import-validation Lint skips validating that
the pod can be imported
--skip-tests Lint skips building and
running tests during
validation
--silent Show nothing
--verbose Show more debugging
information
--no-ansi Show output without ANSI
codes
--help Show help banner of
specified command
➜ pod list --help
Usage:
$ pod list
Lists all available pods.
Options:
--update Run `pod repo update` before listing
--stats Show additional stats (like GitHub watchers and forks)
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod outdated --help
Usage:
$ pod outdated
Shows the outdated pods in the current Podfile.lock, but only those from
spec repos, not those from local/external sources.
Options:
--project-directory=/project/dir/ The path to the root of the project
directory
--no-repo-update Skip running `pod repo update` before
install
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod plugins --help
Usage:
$ pod plugins [COMMAND]
Lists or searches the available CocoaPods plugins and show if you have
them installed or not.
Also allows you to quickly create a new Cocoapods plugin using a provided
template.
Commands:
+ create Creates a new plugin
+ installed List plugins installed on your machine
> list List all known plugins
+ publish Request to add the plugin to the official plugins list
+ search Search for known plugins
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod plugins create --help
Usage:
$ pod plugins create NAME [TEMPLATE_URL]
Creates a scaffold for the development of a new plugin named `NAME`
according to the CocoaPods best practices.
If a `TEMPLATE_URL`, pointing to a git repo containing a compatible
template, is specified, it will be used in place of the default one.
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ pod plugins installed --help
Usage:
$ pod plugins installed
List all installed plugins and their respective version.
Options:
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod plugins list --help
Usage:
$ pod plugins list
List all known plugins (according to the list hosted on
github.com/CocoaPods/cocoapods-plugins)
Options:
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod plugins publish --help
Usage:
$ pod plugins publish
This command is only useful for developers of CocoaPods plugins.
It opens a new GitHub issue to request adding the plugin currently being
developped to the list of official plugins.
The current directory is expected to have one (and only one) `.gemspec`
file describing the CocoaPods plugin gem.
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod plugins search --help
Usage:
$ pod plugins search QUERY
Searches plugins whose 'name' contains the given `QUERY`. `QUERY` is a
regular expression, ignoring case.
With `--full`, it also searches by 'author' and 'description'.
Options:
--full Search by name, author, and description
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod repo --help
Usage:
$ pod repo [COMMAND]
Manage spec-repositories
Commands:
+ add Add a spec repo
+ lint Validates all specs in a repo
> list List repos
+ push Push new specifications to a spec-repo
+ remove Remove a spec repo
+ update Update a spec repo
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod repo add --help
Usage:
$ pod repo add NAME URL [BRANCH]
Clones `URL` in the local spec-repos directory at `~/.cocoapods/repos/`.
The remote can later be referred to by `NAME`.
Options:
--progress Show the progress of cloning the spec repository
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod repo lint --help
Usage:
$ pod repo lint [NAME|DIRECTORY]
Lints the spec-repo `NAME`. If a directory is provided it is assumed to be
the root of a repo. Finally, if `NAME` is not provided this will lint all
the spec-repos known to CocoaPods.
Options:
--only-errors Lint presents only the errors
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod repo list --help
Usage:
$ pod repo list
List the repos from the local spec-repos directory at
`~/.cocoapods/repos/.`
Options:
--count-only Show the total number of repos
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod repo push --help
Usage:
$ pod repo push REPO [NAME.podspec]
Validates `NAME.podspec` or `*.podspec` in the current working dir,
creates a directory and version folder for the pod in the local copy of
`REPO` (~/.cocoapods/repos/[REPO]), copies the podspec file into the
version directory, and finally it pushes `REPO` to its remote.
Options:
--allow-warnings Allows pushing even if
there are warnings
--use-libraries Linter uses static
libraries to install the
spec
--sources=https://github.com/artsy/Specs,master The sources from which to
pull dependent pods
(defaults to all available
repos). Multiple sources
must be comma-delimited.
--local-only Does not perform the step
of pushing REPO to its
remote
--no-private Lint includes checks that
apply only to public repos
--skip-import-validation Lint skips validating that
the pod can be imported
--skip-tests Lint skips building and
running tests during
validation
--commit-message="Fix bug in pod" Add custom commit message.
Opens default editor if no
commit message is
specified.
--use-json Push JSON spec to repo
--swift-version=VERSION The SWIFT_VERSION that
should be used when
linting the spec. This
takes precedence over a
.swift-version file.
--silent Show nothing
--verbose Show more debugging
information
--no-ansi Show output without ANSI
codes
--help Show help banner of
specified command
➜ ~ pod repo remove --help
Usage:
$ pod repo remove NAME
Deletes the remote named `NAME` from the local spec-repos directory at
`~/.cocoapods/repos/.`
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod repo update --help
Usage:
$ pod repo update [NAME]
Updates the local clone of the spec-repo `NAME`. If `NAME` is omitted this
will update all spec-repos in `~/.cocoapods/repos`.
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod search --help
Usage:
$ pod search QUERY
Searches for pods, ignoring case, whose name, summary, description, or
authors match `QUERY`. If the `--simple` option is specified, this will
only search in the names of the pods.
Options:
--regex Interpret the `QUERY` as a regular expression
--simple Search only by name
--stats Show additional stats (like GitHub watchers and forks)
--web Searches on cocoapods.org
--ios Restricts the search to Pods supported on iOS
--osx Restricts the search to Pods supported on macOS
--watchos Restricts the search to Pods supported on watchOS
--tvos Restricts the search to Pods supported on tvOS
--no-pager Do not pipe search results into a pager
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod setup --help
Usage:
$ pod setup
Creates a directory at `~/.cocoapods/repos` which will hold your
spec-repos. This is where it will create a clone of the public `master`
spec-repo from:
https://github.com/CocoaPods/Specs
If the clone already exists, it will ensure that it is up-to-date.
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod spec --help
Usage:
$ pod spec COMMAND
Manage pod specs
Commands:
+ cat Prints a spec file
+ create Create spec file stub.
+ edit Edit a spec file
+ lint Validates a spec file
+ which Prints the path of the given spec
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod spec cat --help
Usage:
$ pod spec cat [QUERY]
Prints the content of the podspec(s) whose name matches `QUERY` to
standard output.
Options:
--regex Interpret the `QUERY` as a regular expression
--show-all Pick from all versions of the given podspec
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod spec create --help
Usage:
$ pod spec create [NAME|https://github.com/USER/REPO]
Creates a PodSpec, in the current working dir, called `NAME.podspec'. If a
GitHub url is passed the spec is prepopulated.
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod spec edit --help
Usage:
$ pod spec edit [QUERY]
Opens the podspec matching `QUERY` to be edited.
Options:
--regex Interpret the `QUERY` as a regular expression
--show-all Pick from all versions of the given podspec
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod spec lint --help
Usage:
$ pod spec lint [NAME.podspec|DIRECTORY|http://PATH/NAME.podspec ...]
Validates `NAME.podspec`. If a `DIRECTORY` is provided, it validates the
podspec files found, including subfolders. In case the argument is
omitted, it defaults to the current working dir.
Options:
--quick Lint skips checks that
would require to download
and build the spec
--allow-warnings Lint validates even if
warnings are present
--subspec=NAME Lint validates only the
given subspec
--no-subspecs Lint skips validation of
subspecs
--no-clean Lint leaves the build
directory intact for
inspection
--fail-fast Lint stops on the first
failing platform or
subspec
--use-libraries Lint uses static libraries
to install the spec
--sources=https://github.com/artsy/Specs,master The sources from which to
pull dependent pods
(defaults to
https://github.com/CocoaPods/Specs.git).
Multiple sources must be
comma-delimited.
--private Lint skips checks that
apply only to public specs
--swift-version=VERSION The SWIFT_VERSION that
should be used to lint the
spec. This takes
precedence over a
.swift-version file.
--skip-import-validation Lint skips validating that
the pod can be imported
--skip-tests Lint skips building and
running tests during
validation
--silent Show nothing
--verbose Show more debugging
information
--no-ansi Show output without ANSI
codes
--help Show help banner of
specified command
➜ ~ pod spec which --help
Usage:
$ pod spec which [QUERY]
Prints the path of the .podspec file(s) whose name matches `QUERY`
Options:
--regex Interpret the `QUERY` as a regular expression
--show-all Print all versions of the given podspec
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod trunk --help
Usage:
$ pod trunk COMMAND
Interact with the CocoaPods API (e.g. publishing new specs)
Commands:
+ add-owner Add an owner to a pod
+ delete Deletes a version of a pod.
+ deprecate Deprecates a pod.
+ info Returns information about a Pod.
+ me Display information about your sessions
+ push Publish a podspec
+ register Manage sessions
+ remove-owner Remove an owner from a pod
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod trunk add-owner --help
Usage:
$ pod trunk add-owner POD OWNER-EMAIL
Adds the registered user with specified `OWNER-EMAIL` as an owner of the
given `POD`. An ‘owner’ is a registered user whom is allowed to make
changes to a pod, such as pushing new versions and adding and removing
other ‘owners’.
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod trunk delete --help
Usage:
$ pod trunk delete NAME VERSION
WARNING: It is generally considered bad behavior to remove versions of a
Pod that others are depending on! Please consider using the deprecate
command instead.
Deletes the specified pod version from trunk and the master specs repo.
Once deleted, this version can never be pushed again.
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod trunk deprecate --help
Usage:
$ pod trunk deprecate NAME
Deprecates a pod.
Options:
--in-favor-of=OTHER_NAME The pod to deprecate this pod in favor of.
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod trunk info --help
Usage:
$ pod trunk info NAME
Returns information about a Pod.
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod trunk me --help
Usage:
$ pod trunk me COMMAND
Includes information about your registration, followed by all your
sessions.
These are your current session, other valid sessions, unverified sessions,
and expired sessions.
Commands:
+ clean-sessions Remove sessions
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod trunk me clean-sessions --help
Usage:
$ pod trunk me clean-sessions
By default this will clean-up your sessions by removing expired and
unverified sessions.
To remove all your sessions, except for the one you are currently using,
specify the `--all` flag.
Options:
--all Removes all your sessions, except for the current one
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod trunk push --help
[!] No podspec found in directory `.`
Usage:
$ pod trunk push [PATH]
Publish the podspec at `PATH` to make it available to all users of the
‘master’ spec-repo. If `PATH` is not provided, defaults to the current
directory.
Before pushing the podspec to cocoapods.org, this will perform a local
lint of the podspec, including a build of the library. However, it remains
*your* responsibility to ensure that the published podspec will actually
work for your users. Thus it is recommended that you *first* try to use
the podspec to integrate the library into your demo and/or real
application.
If this is the first time you publish a spec for this pod, you will
automatically be registered as the ‘owner’ of this pod. (Note that ‘owner’
in this case implies a person that is allowed to publish new versions and
add other ‘owners’, not necessarily the library author.)
Options:
--allow-warnings Allows push even if there are lint warnings
--use-libraries Linter uses static libraries to install the spec
--swift-version=VERSION The SWIFT_VERSION that should be used to lint the
spec. This takes precedence over a .swift-version
file.
--skip-import-validation Lint skips validating that the pod can be
imported
--skip-tests Lint skips building and running tests during
validation
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod trunk register --help
Usage:
$ pod trunk register EMAIL [YOUR_NAME]
Register a new account, or create a new session.
If this is your first registration, both an `EMAIL` address and
`YOUR_NAME` are required. If you’ve already registered with trunk, you may
omit the `YOUR_NAME` (unless you would like to change it).
It is recommended that you provide a description of the session, so that
it will be easier to identify later on. For instance, when you would like
to clean-up your sessions. A common example is to specify the location
where the machine, that you are using the session for, is physically
located.
Examples:
$ pod trunk register eloy@example.com 'Eloy Durán' --description='Personal Laptop'
$ pod trunk register eloy@example.com --description='Work Laptop'
$ pod trunk register eloy@example.com
Options:
--description=DESCRIPTION An arbitrary description to easily identify your
session later on.
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod trunk remove-owner --help
Usage:
$ pod trunk remove-owner POD OWNER-EMAIL
Removes the user with specified `OWNER-EMAIL` from being an owner of the
given `POD`. An ‘owner’ is a registered user whom is allowed to make
changes to a pod, such as pushing new versions and adding and removing
other ‘owners’.
Options:
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod try --help
Usage:
$ pod try NAME|URL
Downloads the Pod with the given `NAME` (or Git `URL`), install its
dependencies if needed and opens its demo project. If a Git URL is
provided the head of the repo is used.
If a Git URL is specified, then a --podspec_name can be provided, if the
podspec name is different than the git repo for some reason.
Options:
--podspec_name=[name] The name of the podspec file within the Git
Repository
--no-repo-update Skip running `pod repo update` before install
--silent Show nothing
--verbose Show more debugging information
--no-ansi Show output without ANSI codes
--help Show help banner of specified command
➜ ~ pod update --help
Usage:
$ pod update [POD_NAMES ...]
Updates the Pods identified by the specified `POD_NAMES`. If no
`POD_NAMES` are specified it updates all the Pods ignoring the contents of
the Podfile.lock. This command is reserved to the update of dependencies
and pod install should be used to install changes to the Podfile.
Options:
--sources=https://github.com/artsy/Specs,master The sources from which to
update dependent pods.
Multiple sources must be
comma-delimited. The
master repo will not be
included by default with
this option.
--project-directory=/project/dir/ The path to the root of
the project directory
--no-repo-update Skip running `pod repo
update` before install
--silent Show nothing
--verbose Show more debugging
information
--no-ansi Show output without ANSI
codes
--help Show help banner of
specified command
扫一扫
1645
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
