Pear DocsHow To
Goal-oriented recipes for getting things done with Pear. Each guide solves one specific problem from start to finish.
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, setting up multisig releases, or troubleshooting common issues.
If you want to look up a CLI flag, an API, or a config field, that's Reference. For the conceptual "why," see About Pear.
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 Bare tab—they apply whether or not your app happens to be a Pear app.
Pear runs on Bare. Bare is the zero-core JavaScript runtime underneath the platform, and it has its own docs: the peer-to-peer building blocks, embedding in native and mobile apps, and compiling to a standalone binary all live on the Bare tab. How Pear and Bare fit together maps the layers.
In this section
- Browse commands with the interactive menu—find and run CLI commands from a filterable list and a form, instead of memorizing flags.
- Manage installed applications—list installed Pear apps and reset their storage.
- Migrate a Node.js app to Bare—port an existing Node.js app to run on Bare.
- Troubleshoot common issues—fixes for common Pear and Bare development issues.
Releasing & distributing your app
CI / GitHub Actions
Build & package
Manual deployment
Multisig
Maintenance