> For the complete documentation index, see [llms.txt](https://umber.gitbook.io/umber/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://umber.gitbook.io/umber/guides/managing-deployments.md). # Managing Deployments Once an asset has more than a couple of versions or environments, deploying one version at a time from its own page gets slow. **Manage Deployments** gives you every environment and every version of an asset in one view, so you can deploy, promote, or take anything offline without navigating away. ## Opening it From the asset's detail page, click the grid icon labeled **Manage Deployments** next to **View Deployment Flow**. This opens `/virtualassets//deployments`. ## Layout * **Left — Environments.** Every environment for your domain, each with a small hint showing what it's currently serving (e.g. `→ WEB2`), or "not deployed" if nothing's live there yet. Click one to select it. * **Right — All versions.** Every version of the asset for the selected environment and platform, newest first. If the asset has versions on more than one target platform (`web`, `ios`, `android`, `generic`), a row of tabs sits above the version list — platform belongs to the version, not the environment, so switching tabs never changes what's selected on the left. ## Reading a version's row Each row shows a thumbnail (a real preview for images and videos — click it to open a larger preview; other file types show a generic icon and aren't clickable), the version ID, and a state badge: | Badge | Meaning | | ------------ | -------------------------------------------------------- | | **Live** | Deployed to this environment and servable. | | **Offline** | Deployed to this environment but not currently servable. | | *(no badge)* | Never deployed to this environment. | The **current default** — the version this environment actually serves when its URL is requested — isn't a badge. It's a green border running through the row, with a pointer marker and a **Default** label breaking the border line, and it moves (animated) the moment a different version becomes default. See [Deployment States](/umber/concepts/deployment-states.md) for why default is shown this way instead of as a fourth badge. ## Actions Which buttons a row shows depends on that version's current state in the selected environment: | Row state | Action | Effect | | ----------------- | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Not deployed here | **Deploy Here** | Deploys the version to this environment as Live. | | Live, not default | **Take Offline** | Marks the version Offline in this environment. | | Live, not default | **Set Default** | Promotes this version to the environment's default. If another version already holds that position, it's demoted and stays Live; if nothing is default yet, this is simply the channel's first promotion. | | Offline | **Set Live** | Marks the version Live again. | | Current default | **Revert** | Reverts the environment's default back to whichever version it pointed to immediately before this promotion. Only reverts one step — if that previous version is no longer Live, the revert is rejected. | A confirmation dialog appears before **Set Default** and **Revert**, since both change what a live URL serves. {% hint style="info" %} You can't take the current default offline directly — revert it first, then take the demoted version offline if you want to. {% endhint %} ## The deployment URL Once an environment and platform are selected, a URL bar appears showing the exact public URL this channel serves and which version it currently points to, with a copy button. It only appears once there's an actual URL to show. ## Deployment history Click the clock icon in the version list's header to open **Deployment History** — a running log of every deploy, promotion, offline, and revert for the selected environment and platform, newest first, with who made the change and when. History starts from when this feature shipped; nothing before that was recorded. Entries are kept for 90 days. ## See also * [Deployment States](/umber/concepts/deployment-states.md) — what Live, Offline, and default mean and how they relate. * [Environments](/umber/concepts/environments.md) — what an environment is. * [Quickstart](/umber/getting-started/quickstart.md) — deploying a single version for the first time. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://umber.gitbook.io/umber/guides/managing-deployments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.