Getting started
Install the pear CLI, then ship an app you already have—build, stage, provision, and seed a release that users get over the air.
This page gets the pear CLI onto your machine and points you at how to build, stage, provision, and seed a release of an app you already have. Don't have an app yet? Build one on P2P—a type-along tutorial that builds a peer-to-peer chat app from scratch, then reshapes it into the production hello-pear-electron scaffold this page's release steps assume.
Install Pear
Get the pear CLI from install.pears.com:
curl https://install.pears.com/pear.sh | shFollow the PATH instructions the installer prints, then run pear directly. See Install & upgrade for the Homebrew and npm-global notes and upgrade details. The tetherto/pear image runs Pear inside Ubuntu with pear and pear-install ready to go—handy for trying the CLI without installing anything locally.
New to the CLI? Run pear --menu (Pear 3.2.0+) to browse every command from a filterable list and fill in its flags as a form, instead of memorizing them. See Browse commands with the interactive menu.
Don't have an app yet?
Clone an official boilerplate instead of starting from a blank folder—each one embeds a pear-runtime-family module for peer-to-peer over-the-air updates, so the release steps below apply as soon as you've made one yours.
hello-pear-electron (desktop)
An Electron GUI app: renderer ↔ main ↔ Bare worker behind a preload bridge. The shape Keet and PearPass ship.
hello-pear-bare (long-running terminal)
A standalone Bare executable for long-running programs: services, REPLs, and TUIs with no GUI and no peer dependencies.
hello-pear-daemon (short-lived CLI)
A standalone Bare executable for commands that run and exit: a detached bare-daemon updater checks for updates in the background after the command returns.
hello-pear-qvac-tui (on-device AI terminal)
A terminal app that runs a language model on the user's own machine: Bare, QVAC on-device inference, and a bare-tui interface, with over-the-air updates.
hello-pear-react-native (mobile)
An Expo/React Native app: a Bare worklet embedded via pear-mobile, with the same over-the-air updates.
Prefer to build the peer-to-peer logic yourself first, rather than clone a template? Build a peer-to-peer chat is the full type-along tutorial.
Already have a built app? Ship it
The deep, step-by-step guides for every part of the release pipeline already exist as how-tos—this section signposts into them rather than repeating them:
- Deploy your application—
pear touch,pear stage,pear provision, andpear seed, the core stage → provision → seed flow. - Build & package—desktop distributables, binaries, and app-store submissions.
- CI/CD with GitHub Actions—automate the same flow from CI.
- Multisig—require multiple signers before a production release goes live.
For the concepts behind that flow—what staging, provisioning, and multisig actually do and why—see Release pipeline.
Where to go next
- Build a peer-to-peer chat—the full type-along tutorial, if you're starting from nothing.
- Command Line Interface (CLI)—every
pearcommand and flag. - Manage installed applications—list installed Pear apps and reset their storage.
- Troubleshoot common issues—fixes for common Pear CLI and deployment issues.
Last updated on