### AppZung CLI: Usage Example

Source: https://unpkg.com/@appzung/cli/README

Demonstrates the basic installation and usage of the AppZung CLI. It shows how to install the CLI globally and execute commands.

```sh-session
$ npm install -g @appzung/cli
$ appzung COMMAND
running command...
$ appzung (--version)
@appzung/cli/1.10.0 linux-x64 node-v22.16.0
$ appzung --help [COMMAND]
USAGE
  $ appzung COMMAND
...
```

--------------------------------

### Install AppZung CLI

Source: https://github.com/appzung

Installs the AppZung Command Line Interface globally using npm. This is the first step to manage your CodePush deployments and interact with the platform.

```Shell
npm install -g @appzung/cli@1
```

--------------------------------

### AppZung CLI Commands

Source: https://github.com/appzung

Provides essential commands for interacting with the AppZung CodePush platform. Includes commands for initiating the welcome guide and migrating from AppCenter CodePush.

```Shell
appzung welcome

```

```Shell
appzung codepush migrate

```

--------------------------------

### AppZung CLI Installation and Usage

Source: https://context7_llms

This snippet covers the installation and basic usage of the AppZung CLI, a command-line interface for managing CodePush deployments. It is essential for developers interacting with the AppZung platform programmatically.

```bash
npm install -g @appzung/cli

# Initialize AppZung in your project
appzung init

# Deploy an update
appzung release "v1.0.0" --description "Initial release"
```

--------------------------------

### Install @appzung/react-native-code-push v5-v9

Source: https://raw.githubusercontent.com/AppZung/react-native-code-push/refs/heads/main/README

Instructions for updating your project's package.json to use specific older versions of @appzung/react-native-code-push (e.g., v9.0.2, 8.3.2, 7.1.1, 6.4.2, 6.3.1, 5.7.1). This is followed by standard package installation commands.

```javascript
{
  "dependencies": {
    "react-native-code-push": "npm:@appzung/react-native-code-push@^8.3.2"
  }
}
```

```bash
npm install
# or
yarn install

bundle exec pod install
```

--------------------------------

### AppZung CLI Basic Commands

Source: https://raw.githubusercontent.com/AppZung/react-native-code-push/refs/heads/main/README

Provides essential commands for interacting with the AppZung CLI. These commands are used for initial setup, getting help, and managing app updates.

```shell
npx @appzung/cli@1 welcome
npx @appzung/cli@1 --help
```

--------------------------------

### appzung autocomplete command

Source: https://unpkg.com/@appzung/cli/README

Displays instructions for installing shell autocompletion for the Appzung CLI. Supports Zsh, Bash, and PowerShell, with an option to refresh the cache.

```APIDOC
appzung autocomplete [SHELL]

Display autocomplete installation instructions.

USAGE
  $ appzung autocomplete [SHELL] [-r]

ARGUMENTS
  SHELL  (zsh|bash|powershell) Shell type

FLAGS
  -r, --refresh-cache  Refresh cache (ignores displaying instructions)

DESCRIPTION
  Display autocomplete installation instructions.

EXAMPLES
  $ appzung autocomplete

  $ appzung autocomplete bash

  $ appzung autocomplete zsh

  $ appzung autocomplete powershell

  $ appzung autocomplete --refresh-cache
```

--------------------------------

### Install AppZung CodePush Packages (sh)

Source: https://raw.githubusercontent.com/AppZung/expo-config-code-push/refs/heads/main/README

Installs the core `@appzung/react-native-code-push` and the `@appzung/expo-config-code-push` packages. This command ensures both the runtime and configuration parts of the CodePush integration are available for your Expo project.

```sh
npx expo install @appzung/react-native-code-push @appzung/expo-config-code-push
```

--------------------------------

### Install Expo Build Properties (sh)

Source: https://raw.githubusercontent.com/AppZung/expo-config-code-push/refs/heads/main/README

Installs the `expo-build-properties` package, which is optionally required to set the iOS deployment target for older Expo projects. This command uses `npx expo install` for compatibility with Expo managed projects.

```sh
npx expo install expo-build-properties
```

--------------------------------

### Manual Sync with Update Dialog

Source: https://raw.githubusercontent.com/AppZung/react-native-code-push/refs/heads/main/README

Demonstrates manual synchronization using `CodePush.sync()`. This example shows how to trigger an update check on a button press, display an update dialog, and install the update immediately. The app is configured to check updates manually.

```javascript
import withCodePush, { CheckFrequency, InstallMode, sync } from '@appzung/react-native-code-push';

class MyApp extends Component {
  onButtonPress() {
    sync({
      updateDialog: true,
      installMode: InstallMode.IMMEDIATE,
    });
  }

  render() {
    return (
      <View>
        <TouchableOpacity onPress={this.onButtonPress}>
          <Text>Check for updates</Text>
        </TouchableOpacity>
      </View>
    );
  }
}

export default withCodePush({ checkFrequency: CheckFrequency.MANUAL })(MyApp);
```

--------------------------------

### Install AppZung React Native CodePush

Source: https://raw.githubusercontent.com/AppZung/react-native-code-push/refs/heads/main/README

Installs the AppZung CodePush package for React Native applications using npm. This is the initial step to integrate dynamic update capabilities into your project.

```shell
npm install --save @appzung/react-native-code-push
```

--------------------------------

### AppZung React Native SDK Integration

Source: https://context7_llms

This documentation outlines the integration of the AppZung SDK for React Native applications. It details how to set up the SDK to enable over-the-air updates for your mobile app, including installation and basic configuration steps.

```bash
npm install --save @appzung/react-native-code-push
# or
yarn add @appzung/react-native-code-push
```

```javascript
import codePush from "react-native-code-push";

let codePushOptions = {
  checkFrequency: codePush.CheckFrequency.ON_APP_START,
};

export default codePush(codePushOptions)(App);

```

--------------------------------

### appzung welcome command

Source: https://unpkg.com/@appzung/cli/README

Displays a welcome message for the AppZung CLI. It has no specific flags or parameters.

```APIDOC
USAGE
  $ appzung welcome

DESCRIPTION
  Welcome to AppZung CLI
```

--------------------------------

### Basic CodePush Integration

Source: https://raw.githubusercontent.com/AppZung/react-native-code-push/refs/heads/main/README

Integrates the CodePush plugin with your React Native app's root component. By default, it checks for updates on app start and installs them on the next restart.

```javascript
import withCodePush from '@appzung/react-native-code-push';

const MyApp = () => {};

export default withCodePush(MyApp);
```

--------------------------------

### appzung releases promote command

Source: https://unpkg.com/@appzung/cli/README

Promotes a release from a source release channel to a target release channel. Allows specifying the source version, description, mandatory status, rollout percentage, and target binary version. Requires authentication.

```APIDOC
appzung releases promote

Promote a release from one channel to another

USAGE
  $ appzung releases promote [--source-release-channel <value>] [--target-release-channel <value>]
    [--source-release-version <value>] [--description <value>] [-m] [-x] [-t <value>] [-r <value>] [-s <value>]

FLAGS
  -m, --[no-]mandatory                  Specifies whether this release should be considered mandatory
  -r, --rollout=<value>                 Percentage points of users this release should be available to (eg. 95 for 95%)
  -t, --target-binary-version=<value>   Semver version that specifies the binary app version this release is compatible
                                        with
  -x, --[no-]disabled                   Specifies whether this release should not be immediately downloadable
      --description=<value>             Description of the changes made to the app in this release
      --source-release-channel=<value>  Source release channel (eg.
                                        "myReleaseChannelDescription/c95d7950-228c-4f47-8abb-4e275050ca8e")
      --source-release-version=<value>  Specific version to promote from source release channel
      --target-release-channel=<value>  Target release channel (eg.
                                        "myReleaseChannelDescription/c95d7950-228c-4f47-8abb-4e275050ca8e")

AUTHENTICATION FLAGS
  -s, --api-key=<value>  An API key that has access to this project. If there is a user logged in, the API key will take
                         precedence.
```

--------------------------------

### appzung help command

Source: https://unpkg.com/@appzung/cli/README

Displays help information for the Appzung CLI, including nested commands if requested.

```APIDOC
appzung help [COMMAND]

Display help for appzung.

USAGE
  $ appzung help [COMMAND...] [-n]

ARGUMENTS
  COMMAND...  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for appzung.
```

--------------------------------

### Migrate from AppCenter

Source: https://appzung.com/faq

Command to initiate the migration process from AppCenter to AppZung. This tool helps fetch and select apps from AppCenter and migrate release channels.

```bash
npx @appzung/cli codepush migrate
```

--------------------------------

### Appzung Deploy React Native Help

Source: https://raw.githubusercontent.com/AppZung/react-native-code-push/refs/heads/main/README

Displays help information for the 'appzung releases deploy-react-native' command, outlining its available parameters and usage details.

```shell
appzung releases deploy-react-native --help
```

--------------------------------

### appzung releases deploy-react-native Command

Source: https://unpkg.com/@appzung/cli/README

This command deploys a React Native release to a specified channel. It supports various configurations for signing, rollout percentages, target binary versions, and bundling options. Users can specify descriptions, use Git commit messages, manage duplicate release errors, and control bundling behavior like entry files, output directories, and Hermes engine usage.

```APIDOC
appzung releases deploy-react-native

Deploy a React Native release

USAGE
  $ appzung releases deploy-react-native [-h] [--release-channel <value>] [-r <value>] [-m] [-x] [--disable-duplicate-release-error] [-k <value>] [--description <value>] [--description-from-current-git-commit] [-s <value>] [-t <value>] [--use-package-json-version] [-b <value>] [--development] [--use-hermes] [--use-jsc] [--extra-hermes-flag <value>...] [--extra-bundler-option <value>...] [-e <value>] [-s <value>] [-o <value>] [--react-native-cli-path <value>] [--sentry-sourcemap-debug-id --sourcemap-output-dir <value>] [-g <value>] [--pod-file <value>] [-p <value>] [--xcode-project-file <value>] [--plist-file-prefix <value>] [-c <value>] [--xcode-target-name <value>] [-y]

FLAGS
  -h, --help: Show CLI help.
  -k, --private-key=<value>: Specifies the path to private key file (or the private key string itself) to sign the release with.
  -m, --[no-]mandatory: Specifies whether this release should be considered mandatory.
  -r, --rollout=<value>: Percentage points of users this release should be available to (eg. 95 for 95%).
  -t, --target-binary-version=<value>: Semver version that specifies the binary app version this release is compatible with.
  -x, --[no-]disabled: Specifies whether this release should not be immediately downloadable.
  -y, --yes: Accepts all confirmation prompts.
  --description=<value>: Description of the changes made to the app in this release.
  --description-from-current-git-commit: Use the current git commit message as the release description (truncated at 255 characters). --description takes precedence.
  --disable-duplicate-release-error: When this flag is set, releasing a package that is identical to the latest release will produce a warning instead of an error.
  --release-channel=<value>: Release channel (eg. "myReleaseChannelDescription/c95d7950-228c-4f47-8abb-4e275050ca8e").

REACT NATIVE BUNDLING FLAGS
  -b, --bundle-name=<value>: Name of the generated JS bundle file. If unspecified, the standard bundle name will be used, depending on the specified platform: "main.jsbundle" (iOS), "index.android.bundle" (Android) or "index.windows.bundle" (Windows).
  -e, --entry-file=<value>: Path to the app's entry JavaScript file. If omitted, "index.<platform>.js" and then "index.js" will be used (if they exist).
  -o, --output-dir=<value>: Path to where the bundle should be written. If omitted, the bundle will not be saved on your machine.
  -s, --sourcemap-output=<value>: Path to where the sourcemap for the resulting bundle should be written. If omitted, a sourcemap will not be generated.
  --development: Specifies whether to generate a dev or release build.
  --extra-bundler-option=<value>...: Option that gets passed to react-native bundler. Can be specified multiple times.
  --extra-hermes-flag=<value>...: Flag that gets passed to Hermes, JavaScript to bytecode compiler. Can be specified multiple times.
  --react-native-cli-path=<value>: Path to the React Native CLI script in setups where the CLI is not in the standard location (eg. in a monorepo).
  --sentry-sourcemap-debug-id: Update sourcemap with the bundle debug ID for Sentry.
  --sourcemap-output-dir=<value>: Path to folder where the sourcemap for the resulting bundle should be written. Name of sourcemap file will be generated automatically. This argument will be ignored if "sourcemap-output" argument is provided. If omitted, a sourcemap will not be generated.
  --use-hermes: Force using Hermes engine.
  --use-jsc: Force using JSC engine.

AUTOMATIC DETECTION OF TARGET BINARY VERSION AND HERMES USAGE FLAGS
  -c, --build-configuration-name=<value>: [default: Release] Name of build configuration which specifies the binary version you want to target this release at. For example, "Debug" or "Release".
```

--------------------------------

### appzung projects create command

Source: https://unpkg.com/@appzung/cli/README

Creates a new project within an organization. Requires organization slug and project name. Allows specifying project framework and release type, with an option to skip confirmation.

```APIDOC
appzung projects create

Create a new project

USAGE
  $ appzung projects create [-o <value>] [-n <value>] [--framework CAPACITOR|CORDOVA|ELECTRON|NATIVE|OTHER|REACT_NATIVE|UNITY|XAMARIN] [--releaseType Alpha|Beta|Canary|Demo|Development|Local|Preview|Production|QA|Sandbox|Staging] [-y]

FLAGS
  -y, --yes  Skip confirmation prompt

REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
  -n, --name=<value>          Project name
  -o, --org=<value>           Organization slug
      --framework=<option>    Project framework
                              <options: CAPACITOR|CORDOVA|ELECTRON|NATIVE|OTHER|REACT_NATIVE|UNITY|XAMARIN>
      --releaseType=<option>  Release type (this has no real impact but helps organize projects)
                              <options: Alpha|Beta|Canary|Demo|Development|Local|Preview|Production|QA|Sandbox|Staging>

DESCRIPTION
  Create a new project
```

--------------------------------

### Deploy Expo Release CLI Command

Source: https://unpkg.com/@appzung/cli/README

This entry documents the `appzung releases deploy-expo` command, used to deploy new versions of Expo applications. It outlines the command's signature, all available flags for customization, and provides details on how to specify release channels, manage rollout percentages, set target binary versions, include release descriptions, and configure build-specific options for different platforms.

```APIDOC
COMMAND: appzung releases deploy-expo

DESCRIPTION: Deploy an Expo release.

USAGE:
  $ appzung releases deploy-expo [-h] [--release-channel <value>] [-r <value>] [-m] [-x] [--disable-duplicate-release-error] [-k <value>] [--description <value>] [--description-from-current-git-commit] [-s <value>] [-t <value>] [--use-package-json-version] [--use-app-config-version] [--development] [-s <value>] [--sourcemap-output-dir <value>] [-o <value>] [--expo-cli-path <value>] [-g <value>] [--pod-file <value>] [-p <value>] [--xcode-project-file <value>] [--plist-file-prefix <value>] [-c <value>] [--xcode-target-name <value>] [-y]

FLAGS:
  -h, --help                                 Show CLI help.
  -k, --private-key=<value>                  Specifies the path to private key file (or the private key string itself) to sign the release with.
  -m, --[no-]mandatory                       Specifies whether this release should be considered mandatory.
  -r, --rollout=<value>                      Percentage points of users this release should be available to (eg. 95 for 95%).
  -t, --target-binary-version=<value>        Semver version that specifies the binary app version this release is compatible with.
  -x, --[no-]disabled                        Specifies whether this release should not be immediately downloadable.
  -y, --yes                                  Accepts all confirmation prompts.
      --description=<value>                  Description of the changes made to the app in this release.
      --description-from-current-git-commit  Use the current git commit message as the release description (truncated at 255 characters). --description takes precedence.
      --disable-duplicate-release-error      When this flag is set, releasing a package that is identical to the latest release will produce a warning instead of an error.
      --release-channel=<value>              Release channel (eg. "myReleaseChannelDescription/c95d7950-228c-4f47-8abb-4e275050ca8e").

AUTOMATIC DETECTION OF TARGET BINARY VERSION AND HERMES USAGE FLAGS:
  -c, --build-configuration-name=<value>  [default: Release] Name of build configuration which specifies the binary version you want to target this release at. For example, "Debug" or "Release" (iOS only).
  -g, --gradle-file=<value>               Path to the gradle file which specifies the binary version you want to target this release at (android only).
  -p, --plist-file=<value>                Path to the plist file which specifies the binary version you want to target this release at (iOS only).
      --plist-file-prefix=<value>         Prefix to append to the file name when attempting to find your app's Info.plist file (iOS only).
      --pod-file=<value>                  Path to the cocoapods config file (iOS only).
      --use-app-config-version            Use the version from app.json as the target binary version instead of auto-detecting from native files.
      --use-package-json-version          Use the version from package.json as the target binary version instead of auto-detecting from native files.
      --xcode-project-file=<value>        Path to the Xcode project or project.pbxproj file.
      --xcode-target-name=<value>         Name of target (PBXNativeTarget) which specifies the binary version you want to target this release at (iOS only).

REACT NATIVE BUNDLING FLAGS:
  -o, --output-dir=<value>            Path to where the bundle should be written. If omitted, the bundle will not be saved on your machine.
  -s, --sourcemap-output=<value>      Path to where the sourcemap for the resulting bundle should be written. If omitted, a sourcemap will not be generated.
      --development                   Specifies whether to generate a dev or release build.
      --expo-cli-path=<value>         Path to the Expo CLI script in setups where the CLI is not in the standard location (eg. in a monorepo).
      --sourcemap-output-dir=<value>  Path to folder where the sourcemap for the resulting bundle should be written. Name of sourcemap file will be generated automatically. This argument will be ignored if "sourcemap-output" argument is provided. If omitted, a sourcemap will not be generated.
```

--------------------------------

### appzung releases list command

Source: https://unpkg.com/@appzung/cli/README

Lists releases within a specified release channel. Requires the release channel to be provided. Supports pagination via a page number parameter.

```APIDOC
appzung releases list

List releases in a release channel

USAGE
  $ appzung releases list [--release-channel <value>] [--page <value>]

FLAGS
  --page=<value>  Page

REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
  --release-channel=<value>  Release channel (eg. "myReleaseChannelDescription/c95d7950-228c-4f47-8abb-4e275050ca8e")
```

--------------------------------

### appzung billing subscribe command

Source: https://unpkg.com/@appzung/cli/README

Allows users to subscribe to a plan.

```APIDOC
appzung billing subscribe

Subscribe to a plan

USAGE
  $ appzung billing subscribe

DESCRIPTION
  Subscribe to a plan
```

--------------------------------

### GitHub Code Search Syntax Documentation Link

Source: https://github.com/appzung

Provides a direct link to official documentation explaining the syntax and qualifiers used for advanced GitHub code searches.

```APIDOC
[Search syntax tips](https://docs.github.com/search-github/github-code-search/understanding-github-code-search-syntax)
```

--------------------------------

### Appzung Releases Deploy Command

Source: https://unpkg.com/@appzung/cli/README

Command to deploy a generic release to a specified release channel, with options for rollout percentage, mandatory status, and description.

```APIDOC
appzung releases deploy
  Deploy a generic release

  USAGE
    $ appzung releases deploy -t <value> -c <value> [-h] [--release-channel <value>] [-r <value>] [-m] [-x]
      [--disable-duplicate-release-error] [-k <value>] [--description <value>] [--description-from-current-git-commit]
      [-s <value>]

  FLAGS
    -c, --update-contents-path=<value>         (required) Path to release contents folder
    -h, --help                                 Show CLI help.
    -k, --private-key=<value>                  Specifies the path to private key file (or the private key string itself)
                                               to sign the release with.
    -m, --[no-]mandatory                       Specifies whether this release should be considered mandatory
    -r, --rollout=<value>                      Percentage points of users this release should be available to (eg. 95 for
                                               95%)
    -t, --target-binary-version=<value>        (required) Semver version that specifies the binary app version this
                                               release is compatible with
    -x, --[no-]disabled                        Specifies whether this release should not be immediately downloadable
        --description=<value>                  Description of the changes made to the app in this release
        --description-from-current-git-commit  Use the current git commit message as the release description (truncated at
                                               255 characters). --description takes precedence.
        --disable-duplicate-release-error      When this flag is set, releasing a package that is identical to the latest
                                               release will produce a warning instead of an error
        --release-channel=<value>              Release channel (eg.
                                               "myReleaseChannelDescription/c95d7950-228c-4f47-8abb-4e275050ca8e")

  AUTHENTICATION FLAGS
    -s, --api-key=<value>  An API key that has access to this project. If there is a user logged in, the API key will take
                           precedence.

  DESCRIPTION
    Deploy a generic release
```

--------------------------------

### Manage API Keys and Deploy Releases

Source: https://appzung.com/faq

CLI commands for managing project API keys and deploying React Native releases. An API key is required for authentication in CI/CD pipelines.

```bash
appzung projects api-keys create
```

```bash
appzung release deploy-react-native --api-key YOUR_API_KEY --release-channel CHANNEL_ID
```

--------------------------------

### appzung organizations create command

Source: https://unpkg.com/@appzung/cli/README

Creates a new organization. Requires organization name and email. A confirmation prompt can be skipped with the --yes flag.

```APIDOC
appzung organizations create

Create a new organization

USAGE
  $ appzung organizations create [-n <value>] [-e <value>] [-y]

FLAGS
  -y, --yes  Skip confirmation prompt

REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
  -e, --email=<value>  Organization email
  -n, --name=<value>   Organization name

DESCRIPTION
  Create a new organization
```

--------------------------------

### appzung version command

Source: https://unpkg.com/@appzung/cli/README

Displays the version of the AppZung CLI. It supports optional flags for JSON output and verbose mode, which includes additional system information.

```APIDOC
USAGE
  $ appzung version [--json] [--verbose]

FLAGS
  --verbose  Show additional information about the CLI.

GLOBAL FLAGS
  --json  Format output as json.

FLAG DESCRIPTIONS
  --verbose  Show additional information about the CLI.

    Additionally shows the architecture, node version, operating system, and versions of plugins that the CLI is using.

_See code: [@oclif/plugin-version](https://github.com/oclif/plugin-version/blob/v2.2.19/src/commands/version.ts)_
```

--------------------------------

### appzung projects api-keys create command

Source: https://unpkg.com/@appzung/cli/README

Creates a new API key for a specific project within an organization. Requires organization and project slugs, and an optional API key name.

```APIDOC
appzung projects api-keys create

Create a new API key for a project

USAGE
  $ appzung projects api-keys create [-o <value>] [-p <value>] [-n <value>]

FLAGS
  -n, --name=<value>  API key name

REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
  -o, --org=<value>      Organization slug
  -p, --project=<value>  Project slug

DESCRIPTION
  Create a new API key for a project
```

--------------------------------

### Appzung Release Channels Commands

Source: https://unpkg.com/@appzung/cli/README

Commands for managing release channels within Appzung, including creating, editing, and listing channels for an application.

```APIDOC
appzung release-channels create
  Create a new release channel

  USAGE
    $ appzung release-channels create [-o <value>] [-p <value>] [-a <value>] [-n <value>] [-y]

  FLAGS
    -y, --yes  Skip confirmation prompt

  REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
    -a, --app=<value>      Application slug
    -n, --name=<value>     Release channel name
    -o, --org=<value>      Organization slug
    -p, --project=<value>  Project slug

  DESCRIPTION
    Create a new release channel

appzung release-channels edit
  Edit a release channel

  USAGE
    $ appzung release-channels edit [--release-channel <value>] [--name <value>]

  FLAGS
    --name=<value>  New release channel name

  REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
    --release-channel=<value>  Release channel ID

  DESCRIPTION
    Edit a release channel

appzung release-channels list
  List release channels in an application

  USAGE
    $ appzung release-channels list [-o <value>] [-p <value>] [-a <value>] [--page <value>]

  FLAGS
    --page=<value>  Page

  REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
    -a, --app=<value>      Application slug
    -o, --org=<value>      Organization slug
    -p, --project=<value>  Project slug

  DESCRIPTION
    List release channels in an application
```

--------------------------------

### appzung releases show command

Source: https://unpkg.com/@appzung/cli/README

Displays details for a specific release within a release channel. It requires both the release channel and the specific release version.

```APIDOC
USAGE
  $ appzung releases show [--release-channel <value>] [--release-version <value>]

REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
  --release-channel=<value>  Release channel (eg. "myReleaseChannelDescription/c95d7950-228c-4f47-8abb-4e275050ca8e")
  --release-version=<value>  Version number

DESCRIPTION
  Show details about a specific release
```

--------------------------------

### appzung releases edit command

Source: https://unpkg.com/@appzung/cli/README

Allows editing the metadata for an existing release. Supports specifying release channel, version, description, mandatory status, rollout percentage, target binary version, and disabled status. Requires authentication via API key.

```APIDOC
appzung releases edit

Edit the metadata for an existing release

USAGE
  $ appzung releases edit [--release-channel <value>] [--release-version <value>] [--description <value>] [-m] [-x]
    [-t <value>] [-r <value>] [-s <value>]

FLAGS
  -m, --[no-]mandatory                 Specifies whether this release should be considered mandatory
  -r, --rollout=<value>                Percentage points of users this release should be available to (eg. 95 for 95%)
  -t, --target-binary-version=<value>  Semver version that specifies the binary app version this release is compatible
                                       with
  -x, --[no-]disabled                  Specifies whether this release should not be immediately downloadable
      --description=<value>            Description of the changes made to the app in this release

AUTHENTICATION FLAGS
  -s, --api-key=<value>  An API key that has access to this project. If there is a user logged in, the API key will take
                         precedence.

REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
  --release-channel=<value>  Release channel (eg. "myReleaseChannelDescription/c95d7950-228c-4f47-8abb-4e275050ca8e")
  --release-version=<value>  Version number to edit
```

--------------------------------

### CLI Authentication Flags

Source: https://unpkg.com/@appzung/cli/README

Defines the API key argument for authentication. This key grants access to the project and takes precedence over logged-in user credentials.

```APIDOC
AUTHENTICATION FLAGS
  -s, --api-key=<value>
    An API key that has access to this project. If there is a user logged in, the API key will take precedence.
```

--------------------------------

### appzung codepush migrate command

Source: https://unpkg.com/@appzung/cli/README

Migrates data from AppCenter to the Appzung codepush service. Requires an AppCenter API token for authentication.

```APIDOC
appzung codepush migrate

Migrate data from AppCenter

USAGE
  $ appzung codepush migrate [-h] [--appcenter-api-token <value>]

FLAGS
  -h, --help                         Show CLI help.
      --appcenter-api-token=<value>  AppCenter API Token (create one at https://appcenter.ms/settings/apitokens)

DESCRIPTION
  Migrate data from AppCenter
```

--------------------------------

### Migrate to AppZung CLI

Source: https://appzung.com/what-is-codepush

Command to initiate the migration process from a previous CodePush service to the AppZung platform using its command-line interface. This command is part of the transition strategy for users migrating from services like AppCenter CodePush.

```bash
npx @appzung/cli codepush migrate
```

--------------------------------

### appzung billing manage command

Source: https://unpkg.com/@appzung/cli/README

Provides access to manage the user's subscription and billing information.

```APIDOC
appzung billing manage

Manage your subscription and billing info

USAGE
  $ appzung billing manage

DESCRIPTION
  Manage your subscription and billing info
```

--------------------------------

### Crisp Chat Initialization Script

Source: https://appzung.com/faq

This script initializes the Crisp chat widget by setting the website ID and loading the Crisp chat library. It's a standard integration snippet for the Crisp customer service platform.

```javascript
(function(){
    const websiteId = "8478d512-cce9-4063-a97c-b7e211d67ea5";
    window.$crisp = [];
    window.CRISP_WEBSITE_ID = websiteId;
    (function () {
        d = document;
        s = d.createElement("script");
        s.src = "https://client.crisp.chat/l.js";
        s.async = 1;
        d.getElementsByTagName("head")[0].appendChild(s);
    })();
})();
```

--------------------------------

### Appzung Projects Commands

Source: https://unpkg.com/@appzung/cli/README

Commands for managing projects within Appzung, including editing project details and listing projects in an organization.

```APIDOC
appzung projects edit
  Edit a project

  USAGE
    $ appzung projects edit [-o <value>] [-p <value>] [--name <value>] [--framework CAPACITOR|CORDOVA|ELECTRON|NATIVE|OTHER|REACT_NATIVE|UNITY|XAMARIN] [--releaseType Alpha|Beta|Canary|Demo|Development|Local|Preview|Production|QA|Sandbox|Staging]

  FLAGS
    --framework=<option>    New project framework
                            <options: CAPACITOR|CORDOVA|ELECTRON|NATIVE|OTHER|REACT_NATIVE|UNITY|XAMARIN>
    --name=<value>          New project name
    --releaseType=<option>  New release type
                            <options: Alpha|Beta|Canary|Demo|Development|Local|Preview|Production|QA|Sandbox|Staging>

  REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
    -o, --org=<value>      Organization slug
    -p, --project=<value>  Project slug

  DESCRIPTION
    Edit a project

appzung projects list
  List projects in an organization

  USAGE
    $ appzung projects list [-o <value>] [--page <value>]

  FLAGS
    --page=<value>  Page

  REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
    -o, --org=<value>  Organization slug

  DESCRIPTION
    List projects in an organization
```

--------------------------------

### AppZung CLI: Applications Management

Source: https://unpkg.com/@appzung/cli/README

Commands for managing applications within AppZung projects. This includes creating new applications, editing existing ones, and listing applications associated with a project.

```APIDOC
appzung applications create
  Create a new application

  USAGE
    $ appzung applications create [-o <value>] [-p <value>] [-n <value>] [--platform android|ios|macos|other|tvos|windows]
      [-y]

  FLAGS
    -y, --yes  Skip confirmation prompt

  REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
    -n, --name=<value>       Application name
    -o, --org=<value>        Organization slug
    -p, --project=<value>    Project slug
        --platform=<option>  Application platform
                           <options: android|ios|macos|other|tvos|windows>

  DESCRIPTION
    Create a new application

appzung applications edit
  Edit an application

  USAGE
    $ appzung applications edit [-o <value>] [-p <value>] [-a <value>] [--name <value>] [--platform
      android|ios|macos|other|tvos|windows]

  FLAGS
    --name=<value>       New application name
    --platform=<option>  New application platform
                       <options: android|ios|macos|other|tvos|windows>

  REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
    -a, --app=<value>      Application slug
    -o, --org=<value>      Organization slug
    -p, --project=<value>  Project slug

  DESCRIPTION
    Edit an application

appzung applications list
  List applications in a project

  USAGE
    $ appzung applications list [-o <value>] [-p <value>] [--page <value>]

  FLAGS
    --page=<value>  Page

  REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
    -o, --org=<value>      Organization slug
    -p, --project=<value>  Project slug

  DESCRIPTION
    List applications in a project
```

--------------------------------

### appzung organizations api-keys create command

Source: https://unpkg.com/@appzung/cli/README

Creates a new API key for a specified organization. The API key name is optional.

```APIDOC
appzung organizations api-keys create

Create a new API key for an organization

USAGE
  $ appzung organizations api-keys create [-o <value>] [-n <value>]

FLAGS
  -n, --name=<value>  API key name

REQUIRED IN NON-INTERACTIVE TERMINALS FLAGS
  -o, --org=<value>  Organization slug

DESCRIPTION
  Create a new API key for an organization
```

--------------------------------

### appzung organizations list command

Source: https://unpkg.com/@appzung/cli/README

Lists all organizations associated with the current user. Supports pagination.

```APIDOC
appzung organizations list

List your organizations

USAGE
  $ appzung organizations list [--page <value>]

FLAGS
  --page=<value>  Page

DESCRIPTION
  List your organizations
```

--------------------------------

### Appzung CI Deployment for React Native (Android/iOS)

Source: https://raw.githubusercontent.com/AppZung/react-native-code-push/refs/heads/main/README

Commands for deploying React Native updates via CI using Appzung. These commands specify release channels, use the current Git commit for descriptions, enable Hermes, disable duplicate release errors, and require an API key for both Android and iOS platforms.

```shell
appzung releases deploy-react-native --release-channel $APPZUNG_RELEASE_CHANNEL_ID_ANDROID --description-from-current-git-commit --use-hermes --disable-duplicate-release-error --api-key $APPZUNG_API_KEY
```

```shell
appzung releases deploy-react-native --release-channel $APPZUNG_RELEASE_CHANNEL_ID_IOS --description-from-current-git-commit --use-hermes --disable-duplicate-release-error --api-key $APPZUNG_API_KEY
```

--------------------------------

### Appzung API References

Source: https://raw.githubusercontent.com/AppZung/react-native-code-push/refs/heads/main/README

Links to detailed API documentation for Appzung's CodePush functionality across different platforms. Includes references for JavaScript, Objective-C (iOS), and Java (Android).

```APIDOC
JavaScript API:
  Refer to docs/api-js/README.md for JavaScript API details.

Objective-C API Reference (iOS):
  Refer to docs/api-ios.md for Objective-C API details.

Java API Reference (Android):
  Refer to docs/api-android.md for Java API details.
```

--------------------------------

### Initialize Simple Analytics Event

Source: https://console.appzung.com/

Initializes the Simple Analytics event tracking function. It queues events if the function is called before the script loads, ensuring no events are lost.

```javascript
window.sa_event=window.sa_event||function(){var a=[].slice.call(arguments);window.sa_event.q?window.sa_event.q.push(a):window.sa_event.q=[a]};
```

--------------------------------

### appzung releases rollback command

Source: https://unpkg.com/@appzung/cli/README

Rolls back a release channel to a previous release version. It requires a release channel and optionally accepts a target release version. An API key is needed for authentication.

```APIDOC
USAGE
  $ appzung releases rollback [--release-channel <value>] [--target-release-version <value>] [-s <value>]

FLAGS
  --release-channel=<value>         Release channel (eg.
                                    "myReleaseChannelDescription/c95d7950-228c-4f47-8abb-4e275050ca8e")
  --target-release-version=<value>  Specific version to rollback to (defaults to last known version)

AUTHENTICATION FLAGS
  -s, --api-key=<value>  An API key that has access to this project. If there is a user logged in, the API key will take
                         precedence.

DESCRIPTION
  Rollback a release channel to a previous release version
```

--------------------------------

### GitHub Code Search Command Prompt

Source: https://github.com/appzung

Illustrates the primary input field for searching code, repositories, users, issues, and pull requests within GitHub.

```APIDOC
Search or jump to...
Search code, repositories, users, issues, pull requests...
```

--------------------------------

### Initialize Crisp Chat Widget

Source: https://console.appzung.com/

Conditionally initializes the Crisp chat widget based on a website ID. It dynamically loads the Crisp JavaScript library into the page's head.

```javascript
if ( "8478d512-cce9-4063-a97c-b7e211d67ea5" && !"8478d512-cce9-4063-a97c-b7e211d67ea5".includes("%" ) ) { window.$crisp = []; window.CRISP_WEBSITE_ID = "8478d512-cce9-4063-a97c-b7e211d67ea5"; (function () { d = document; s = d.createElement("script"); s.src = "https://client.crisp.chat/l.js"; s.async = 1; d.getElementsByTagName("head")[0].appendChild(s); })(); }
```

--------------------------------

### AppZung CLI Migration and Deployment

Source: https://raw.githubusercontent.com/AppZung/react-native-code-push/refs/heads/main/README

Commands for migrating existing AppCenter CodePush apps to AppZung and deploying React Native updates using the AppZung CLI. This facilitates transitioning to the AppZung platform.

```shell
npx @appzung/cli@1 codepush migrate
npx @appzung/cli@1 releases deploy-react-native
```

--------------------------------

### AppZung CLI: Authentication Management

Source: https://unpkg.com/@appzung/cli/README

Commands for managing user authentication with the AppZung platform. This includes logging in, logging out, and checking the current user's status.

```APIDOC
appzung auth login
  Open login page and retrieve token

  USAGE
    $ appzung auth login [-m]

  FLAGS
    -m, --manual  Skip automatic token listening and use manual token entry

  DESCRIPTION
    Open login page and retrieve token

appzung auth logout
  Logout from the current session

  USAGE
    $ appzung auth logout [--web]

  FLAGS
    --web  Also logout the web session (eg. for a full reauthentication)

  DESCRIPTION
    Logout from the current session

appzung auth whoami
  Show currently logged in user

  USAGE
    $ appzung auth whoami

  DESCRIPTION
    Show currently logged in user
```

--------------------------------

### Crisp Chat Initialization

Source: https://appzung.com/what-is-codepush

JavaScript code snippet to initialize the Crisp chat widget on the webpage. It sets the website ID and asynchronously loads the Crisp chat client script, enabling live chat functionality for users.

```javascript
(function(){
  const websiteId = "8478d512-cce9-4063-a97c-b7e211d67ea5";
  window.$crisp = [];
  window.CRISP_WEBSITE_ID = websiteId;
  (function () {
    d = document;
    s = d.createElement("script");
    s.src = "https://client.crisp.chat/l.js";
    s.async = 1;
    d.getElementsByTagName("head")[0].appendChild(s);
  })();
})();
```

--------------------------------

### AppZung CLI Release Deploy

Source: https://raw.githubusercontent.com/AppZung/react-native-code-push/refs/heads/main/README

Commands for deploying React Native updates using the AppZung CLI. This includes basic deployment, deploying with a changelog from git, forcing specific JS engines (Hermes/JSC), and targeting specific binary versions.

```shell
# Basic deployment
appzung releases deploy-react-native

# Release a mandatory update with a changelog from the last git commit
appzung releases deploy-react-native -m --description-from-current-git-commit

# Force using hermes engine
appzung releases deploy-react-native --use-hermes

# Force using JSC engine
appzung releases deploy-react-native --use-jsc

# Specify target binary version
appzung releases deploy-react-native --target-binary-version "1.1.2"
```