Marketplace Apps

The fireberry marketplace commands publish apps to the public Fireberry marketplace, where any organization can find and install them. This is a separate track from the private-app flow (create → push → deploy → install), which publishes only to your own organization.

The expected flow

You don't start a marketplace app from scratch. Develop your private app first, and once you're satisfied with it, fork it and publish the fork:

cd my-app                                                 # 1. your finished private app
fireberry marketplace clone /Users/me/apps/my-app-market  # 2. fork → new app id
cd /Users/me/apps/my-app-market                           # 3. publish from the clone
fireberry marketplace deploy

Cloning is a one-time step per marketplace app; after that you publish updates with marketplace deploy from the cloned folder.

❗️

Two different apps, two different manifests

The clone is not another version of your private app — it's a separate entity with its own app.id and its own component IDs. Deploying to the marketplace never converts, moves, or promotes the private app.

So you maintain two manifest.yml files in two folders: one for the private app, one for the marketplace app. Run push, deploy, install, and debug in the private folder, and marketplace deploy in the clone — every command acts on the manifest in the current directory. Code changes must be applied and published in each folder separately.

fireberry marketplace clone

Copies the current app into a new folder with a fresh identity, so the copy is an independent app rather than a duplicate of the same one. App and component IDs must be unique across Fireberry, so a plain cp -r would leave you with two folders claiming to be the same app — this is the safe way to fork one.

fireberry marketplace clone [dest-folder]

Requirements: Must be run inside an app directory — it reads manifest.yml from the current directory. No token is needed; clone makes no API calls, so the new app doesn't exist server-side until you deploy it.

What it does:

1. Copies everything from the app folder, skipping node_modules and the destination itself.
2. Rewrites the destination's manifest.yml with a new app UUID and a new UUID for every component.

Everything else carries over unchanged — app name, description, icon, and each component's title, path, type, and settings.

It refuses to run if the destination equals the source, exists as a non-directory, or exists and is non-empty.

⚠️

Pass a full path — a bare folder name will fail

The destination is resolved relative to the current directory, which is your app folder — so a bare name like market-app lands inside the app you're cloning, and an app can't be copied into itself:

$ pwd
/Users/me/fireberry/version-test/sara-version-test
$ fireberry marketplace clone
? Destination folder: market-app
✖ Failed to clone app into "market-app"
Error: Cannot copy '/Users/me/fireberry/version-test/sara-version-test' to a subdirectory
of itself, '/Users/me/fireberry/version-test/sara-version-test/market-app'.

Pass the full path to a folder outside the app instead:

Bash

fireberry marketplace clone /Users/me/fireberry/version-test/market-app

⚠️

node_modules is the only exclusion

.git, .env files, and built dist/ output are all copied — check the clone for secrets before sharing it. Component titles are copied too; only IDs change, so rename them in the new manifest if you want them distinguishable.

fireberry marketplace deploy

Publishes the current app's built components to the public Fireberry marketplace.

fireberry marketplace deploy

cd /Users/me/apps/my-app-market    # the cloned app, not the private one
fireberry marketplace deploy

Requirements: a token from fireberry init, a manifest.yml in the working directory, and components already built — each entry's path must point at existing build output.

What it does:

1. Loads manifest.yml, and validates and reads app.icon if it's set.
2. Validates every component and packages each build as tar.gz — checks that each path exists, that all component IDs are unique, and that each type has its required settings.
3. Prints a per-component summary (title, ID, size in KB), then POSTs to /services/developer/app/marketplace/deploy with { components, manifest, icon }.

Required settings by component type:

Icon rules (when app.icon is set): must be .svg/.png/.jpg/.jpeg, non-empty, and ≤ 500 KB. Its size is reported on success.

⚠️

Run this from the cloned folder

marketplace deploy publishes whatever app the current directory's manifest.yml describes. Run it inside your private app folder and you publish your private app's identity to the public marketplace.

An app with no components is an error, not a graceful skip — validation fails with No components found in manifest and the deploy aborts. The same applies to push.

push vs. deploy vs. marketplace deploy

These three commands sound similar and are the easiest place to go wrong:

marketplace deploy and push send identical payloads — they differ only in destination endpoint, and therefore in which app the payload lands on. Since each reads the manifest.yml in the current directory, running the right command from the wrong folder publishes the wrong app. Confirm which folder you're in before deploying: the private app is updated with push + deploy, and the clone with marketplace deploy.

Troubleshooting

Next Steps

• CLI — Full command reference and the manifest.yml schema
• Local Development — Master the debug workflow
• Component Types — Understand component configurations