Publish and deploy App versions

Publishing and deploying are independent actions. Publish creates a new immutable version and doesn’t start it. Deploy starts a published version, making it reachable by authorized viewers. You can therefore publish several versions before deploying any of them, and redeploy an older version at any time.

Publish a version

Publish from a workspace that has an active Draft App by selecting Publish App (see Develop and test an App), or directly from the App list page without a Draft App. A version captures the App identity and version-defining content listed below. When you publish directly without a Draft, provide an entry point, code commit, Compute Environment and revision, and Hardware Tier. Other fields, such as Data Plane, volume and Dataset configuration, and identity propagation, can use their defaults. The result is a new version in the App’s history, with the Git reference resolved and the commit pinned at publish time.

When you publish into an existing App, the entry point and the code configuration type must match the target App’s. Domino rejects a mismatch. The entry point is fixed for the life of an App, so create a new App to change it.

Deploy a version

Select a version on the App details page and select Deploy. A dialog lets you review and update deployment settings before the version starts. An App has at most one running instance at a time. In that dialog you can set:

Custom URL path for easier sharing (for example, /apps/demo).
Iframe rendering to control whether the App renders inside the Domino iframe wrapper or is served directly at its URL. This setting applies only when deep linking is off. When deep linking is on, Domino serves the App directly at its URL and doesn’t render it in an iframe. Turn iframe rendering off when your framework does not work inside an iframe. Changing this setting restarts the running instance but does not create a new version.
Enable deep linking to let viewers link to a specific view inside the App by appending query parameters to its URL. Apps with deep linking on are never rendered in an iframe. Deep linking needs the SecureIdentityPropagationToAppsEnabled feature flag, so ask your administrator to check Configuration settings for Apps if the option is missing.

Any published version can be deployed, not just the newest. App versioning and reproducibility covers restoring pinned inputs and rolling back to a previous version.

If Governance is enabled and a policy applied to the App gates the Deploy action, the Deploy dialog lists any missing approvals and disables Deploy App version until they are granted. See Govern an App for the full flow.

What creates a version, and what doesn’t

Deployment settings govern how and where an App runs rather than what it runs, so editing them doesn’t produce a version.

Setting group	Fields	Version behavior
App identity	Entry point; code configuration type	Captured by every version, but fixed for the life of the App. Create another App to change either field.
Version-defining content	Source code (the Git reference and resolved commits for the main repository, Domino File System, and imported Project repositories); Compute Environment and environment revision; Data Plane; external data volume mounts; NetApp Volume mounts; Dataset mount configuration; extended identity propagation	Publishing a Draft or editing one of these fields creates a version. The fields are immutable for that version, and an edit stops the running instance.
Deployment settings	Hardware Tier; autoscaling; custom (vanity) URL; iframe rendering, deep linking, and query parameters	Updates the existing version in place and restarts the running instance. No new version is created.
Version metadata	Version description (Version Notes); Tags	Updates the existing version in place without restarting the running instance. No new version is created.

Starting and stopping an App never create a version.

Manage Apps through the API

The /api/apps/v1/ endpoints cover the same operations: create an App, create a Draft App for a workspace, publish, list and create versions, and start, stop, or live-sync a version. Publishing into an App whose entry point or configuration type doesn’t match returns 422. The older /api/apps/beta/ endpoints remain active and unchanged, so existing callers need no migration. App instance reads (list instances, logs, real-time logs, views, and instance delete) are available only on the beta endpoints.

Filter and sort the App list

GET /api/apps/v1/apps and GET /api/apps/beta/apps accept the same query parameters, so you can script an App inventory instead of paging through the UI. Filter by projectId, name, ownerId, status, publisherId, or tagIds, and combine any of them in one request. Two filters answer type and access questions directly:

configurationType keeps only Apps with one configuration type: STANDARD or AISYSTEM.
accessStatus filters Apps by your own access: granted (you can open the App), pending (your access request awaits a decision), or noAccess (no access and no pending request).

Sort with sortField (name, lastUpdated, status, views, lastViewed, or published, the time the App’s current instance was published) and sortOrder (asc or desc). For example, list the Apps you can already open, most recently published first:

import os
import requests

response = requests.get(
    f"{os.environ['DOMINO_API_HOST']}/api/apps/v1/apps",
    headers={"Authorization": f"Bearer {os.environ['DOMINO_API_TOKEN']}"},
    params={
        "accessStatus": "granted",
        "sortField": "published",
        "sortOrder": "desc",
    },
)
response.raise_for_status()

for app in response.json().get("items", []):
    print(app["name"])

Both surfaces are documented in the Domino Platform API reference under the Apps, AppVersions, and AppInstances tags.

Create an App: The two entry points for a new App.
Develop and test an App: Iterate in a workspace before publishing.
Share an App: Control who can discover and open a deployed App.
App versioning and reproducibility: What a version pins and how to start an older one.

Core Concepts

Features

Publish and deploy App versions

Publish a version

Deploy a version

What creates a version, and what doesn’t

Manage Apps through the API

Filter and sort the App list

​Publish a version

​Deploy a version

​What creates a version, and what doesn’t

​Manage Apps through the API

​Filter and sort the App list

​Related

Publish a version

Deploy a version

What creates a version, and what doesn’t

Manage Apps through the API

Filter and sort the App list

Related