Skip to Content
Publish to app store

Publish an app to the NOVA app store

Once you’ve built and tested your app, e.g. a device integration, you can publish it to the NOVA app store with the Wandelbots NOVA CLI .

The NOVA CLI uses an application manifest closely linking to the Wandelbots NOVA API Application endpoints . This manifest is provided by default when you start an app with Typescript or Python templates.

Application manifest

# The name of the app, how it will be displayed on the NOVA homescreen name: rerun # URL Path to an application icon, which will pop up on the NOVA homescreen. # The path starts at the root level. appIcon: app_icon.webp containerImage: # This is the image which will be running your service image: wandelbots.azurecr.io/nova-apps/rerun:0.0.30 # The credentials required to pull images from private registries credentials: registry: wandelbots.azurecr.io user: your-username password: your-password # The port where your app serves the OpenAPI interface, app_icon, and small UI. port: 3001 # Additional environment variables which will be available in the container. environment: - name: ENV_VAR_NAME value: env_var_value # The path and capacity of a volume that retains data across application restarts. # The maximal requestable capacity is 300Mi. If you need more capacity consider using storeObject. storage: mountPath: /data # The amount of local storage available for the application. # NOTE: The capacity can NEVER be reduced! capacity: 100Mi # (Optional) Additional resources that the application requires. resources: # Number of GPUs the application requires (Nvidia GPUs support will be provided soon). intel-gpu: 1

Environment variables

🚨

When NOVA hosts your service in a cell called cell with the app name robo-app, the public base path becomes http://host/cell/robo-app. Respect the provided BASE_PATH so every link in your UI and OpenAPI stays valid.

  • BASE_PATH: URL prefix used to mount your UI and API routes.
  • NOVA_API: Internal endpoint that lets the container talk to NOVA.
  • CELL_NAME: Name of the cell where the service is deployed.
  • NATS_BROKER: a user for your application to commincate with NATS.

Install and observe the service

Apply the manifest with the NOVA CLI:

nova app install your-app.yaml
📡

All manifest parameters, runtime status, resource assignments, and usage metrics are exposed via the List Apps API . Use it to audit deployments or sync them with external tooling.

Once installed, the app tile launches your web UI, and robot programs can call the same endpoints through http:///<my.instance.io>/cell/{app_name} from inside the cell network. For REST-based installs, see the manual deployment section below.

Publish your app in the app store

After validating the integration, submit the manifest to the Wandelbots NOVA catalog .

  1. Open a pull request with the descriptor so it can be reviewed.
  2. Once merged, the service appears in the NOVA app store and can be installed, keeping instances in sync and enabling reuse without repeated setup work.
Last updated on