Appearance
Multiple projects
For organisation membership, app permissions and the separate platform portal, see Organisations and access.
Project configuration
Each project reads its own ota.config.json. There is no global active project. Run commands from the intended app folder, and check the printed app, channel and version before publication.
iOS and Android point to distinct dashboard apps inside that configuration. Staging and Production share their app's signing key, with separate channel IDs.
Signing keys
Private keys are indexed by server and app identity under ~/.pushota. Different projects connected to different apps use different keys. Two checkouts intentionally connected to the same dashboard app share its signing identity.
Back up private keys separately. A server backup contains public signing configuration, not your private release key.
Operator profiles
Expiring login sessions are shared per server on the workstation. For separate operator profiles, set OTA_HOME to a separate protected directory outside the project.
Uninstall removes the current project's integration. Shared keys and sessions are retained so another checkout is not affected.
Existing installations automatically reuse their original private directory, signing keys and installation receipts. Legacy helper filenames and environment variables remain accepted during migration. New projects use the neutral names shown here.