# How To



How-tos are goal-oriented recipes. Each one assumes you already know roughly what you're doing and just need the steps for a particular task—[deploying an app](/pear/how-to/operate-an-app/manual-deployment/deployment), [setting up multisig releases](/pear/how-to/operate-an-app/multisig/set-up-multisig), or [troubleshooting common issues](/pear/how-to/troubleshooting).

If you want to look up a CLI flag, an API, or a config field, that's **[Reference](/pear/reference)**. For the conceptual "why," see **[About Pear](/pear/explanation)**.

This section covers what the `pear` CLI and `pear-*` modules do—building, staging, seeding, provisioning, and updating an app. For the peer-to-peer logic *inside* your app (connecting peers, replicating data, streaming media, managing identity), the guides are on the [P2P tab](/p2p/how-to)—they apply whether or not your app happens to be a Pear app.

<Callout type="info">
  **P2P is the peer-to-peer building blocks.** Hypercore, Hyperswarm, Autobase, Hyperbee, Hyperdrive, HyperDHT, and Corestore—independent JavaScript modules for storage, discovery, and replication, with their own docs on the [P2P tab](/p2p). [How the stack fits together](/p2p/explanation/how-the-stack-fits-together) maps the layers.
</Callout>

## In this section [#in-this-section]

* [Browse commands with the interactive menu](/pear/how-to/browse-commands-with-the-interactive-menu)—find and run CLI commands from a filterable list and a form, instead of memorizing flags.
* [Look up this machine's network keys](/pear/how-to/look-up-network-keys)—read the seed, blind relay, blind peer, and blind peer client keys, and hand the right one to the right peer.
* [Manage installed applications](/pear/how-to/manage-installed-applications)—list installed Pear apps and reset their storage.
* [Migrate a Node.js app to Bare](/bare/how-to/migrate-a-nodejs-app-to-bare)—port an existing Node.js app to run on Bare.
* [Troubleshoot common issues](/pear/how-to/troubleshooting)—fixes for common Pear CLI and deployment issues.

### Releasing & distributing your app [#releasing--distributing-your-app]

**CI / GitHub Actions**

* [Publish with GitHub Actions](/pear/how-to/operate-an-app/github-actions/publish-with-github-actions)
* [Build and sign desktop apps in CI](/pear/how-to/operate-an-app/github-actions/build-and-sign-in-ci)

**Build & package**

* [Build desktop distributables](/pear/how-to/operate-an-app/build-and-package/build-desktop-distributables)
* [Distribute as a binary](/pear/how-to/operate-an-app/build-and-package/distribute-as-binary)
* [Submit to app stores](/pear/how-to/operate-an-app/build-and-package/submit-to-app-stores)

**Manual deployment**

* [Deploy your application](/pear/how-to/operate-an-app/manual-deployment/deployment)
* [Deploy your mobile application](/pear/how-to/operate-an-app/manual-deployment/mobile)
* [Preflight a release before staging](/pear/how-to/operate-an-app/manual-deployment/preflight-a-release)
* [Troubleshoot desktop releases](/pear/how-to/operate-an-app/manual-deployment/troubleshoot-desktop-releases)

**Multisig**

* [Set up multisig](/pear/how-to/operate-an-app/multisig/set-up-multisig)
* [Sign with multisig](/pear/how-to/operate-an-app/multisig/sign-with-multisig)
* [Troubleshoot multisig](/pear/how-to/operate-an-app/multisig/troubleshoot-multisig)

**Maintenance**

* [Migrate from pear run to Pear OTA](/pear/how-to/operate-an-app/migration)