Ship, publish and operate

The manifest, private versus Marketplace, versioning, dependencies, validation, deploying, publish and install, billing, consent, testing, verifying live, and operating the app.

Declare it

Manifest reference

Field-by-field reference for manifest.json — identity, dependencies, contributions, activation.

Private or Marketplace

type — the one-customer custom app versus marketplace distribution.

Versioning

Strict-forward semver, and why a breaking change is a new capability and a new route.

Dependencies

Auto-installed versus prompted, and the vendor/app key rule.

Validate

Validating against schemas.revenexx.com, and the rules that only fail at publish.

Ship it

Deploying

revenexx deploy app end to end, git-wired versus tarball, runtimes and flags.

Publish and install

Why routes are write-at-install, publishing, marketplace installs and upgrades.

Billing

billing.json — free, paid or included, plans, trials, the listing and its limits.

Consent

What the merchant is shown, and what changes when you add a grant.

Prove it, then run it

Testing

The in-memory harness, what mocks miss, and the stricter-contract trap.

Verifying live

Calling through the gateway, the empty-body rule, and /defaults after install.

Operating

The App Studio screens — deployments, executions, variables, usage, traces, settings.

You have written the files. This group is everything after that: how the app gets onto the platform, what publish and install actually do, how a second version reaches a tenant already running the first, and how you run the thing once real traffic hits it.

The path

text

validate ──► deploy ──► build ──► publish ──► install ──► verify ──► operate

revenexx deploy app runs the middle of that in one command. The two ends are yours: validating before you push, and confirming afterwards that the gateway answers.

Routes are written at install time. That single fact explains most of this group. A build that succeeded and a version that published still answer nothing new until the install step runs for that version — which is why deploy app does all of it by default, and why --no-install leaves you wondering where your capability went.

In this group

Manifest reference — every field of manifest.json.
Private or Marketplace — the distinction type draws.
Versioning — strict-forward semver.
Dependencies — needing another app.
Validate — before you deploy, and the publish-time rules.
Deploying — the command and its flags.
Publish and install — what each step really does.
Billing — billing.json.
Consent — the merchant's decision.
Testing — before you ship.
Verifying live — after you ship.
Operating — the screens you live in afterwards.

Your First App in 15 Minutes — the scaffold-to-deployed version of all of this.
Migrations — what a deploy does to your tables.
CLI: scaffolding — create and deploy in the CLI's own words.
Deploy with the CLI — the same loop as a walkthrough.