@pitcher/cli-scripts

@pitcher/cli-scripts

Pitcher CLI Tools provide a suite of command-line utilities to streamline your workflow. For the best experience, we recommend installing the tools globally using npm install -g @pitcher/cli-scripts.

Help

p --help
# or for specific command help:
p command --help

To run the publish-app command:

# Basic usage
p publish-app <folder> --url https://dev.my.pitcher.com --api-key myapikey

# Publish to current folder and dev org
p publish-app --api-key myapikey

# Dry run with version increment
p publish-app --api-key myapikey --dry-run --increment-version

# Publish and install to specific instances
p publish-app --api-key myapikey --increment-version --install-to "01HG0C5NS1BTQ2ZPE1XCGKSGDH, 01HG0C5NS1BTQ2ZPE1XCGKSGDA"

# Publish and install to all instances with a specific environment name
p publish-app --api-key myapikey --increment-version --install-to-env-name "Demo"

# Combine both: install to specific instances AND all instances in an environment
p publish-app --api-key myapikey --increment-version --install-to "01HG0C5NS1BTQ2ZPE1XCGKSGDH" --install-to-env-name "Demo"

# Alternative: Set API key via environment variable
export NG_API_KEY=myapikey
p publish-app --increment-version --install-to-env-name "Production"

Options

• --api-key <apiKey>: API Key for authentication (can also use NG_API_KEY env variable)
• --org <organization>: Organization subdomain (default: "dev")
• --increment-version: Increment version in app.json with timestamp
• --dry-run: Perform a dry run without publishing
• --publish-url <url>: Explicit publish URL
• --install-to <instanceIds>: Comma-separated list of instance IDs to install the app to after publishing
• --install-to-env-name <envName>: Environment name to filter instances and install the app to after publishing (case-insensitive)