> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment.md).
# Deployment
Umbraco Cloud uses a deployment model based on Git, Kudu, and Umbraco Deploy to move changes between environments. This follows a left-to-right deployment approach. Changes start in the local or left-most environment and are deployed to the production/Live environment. This workflow is called the mainline.
The mainline environments are used when building and deploying the initial website. Upgrades, both manual and automatic, also go through the mainline environments.
Flexible environments can be used to work on features separate from the mainline. This is done without interfering with upgrades or other changes being worked on in the mainline.
## Deployment Approach
Umbraco Cloud separates schema and content during deployment. Schema includes Document Types, Templates, Forms, Views, and config files. Content includes content items and media.
* **Deploy:** Moves schema between environments using a Git client or the Umbraco Cloud Portal.
* **Transfer:** Move content and media directly via the Umbraco backoffice.
### Types of Deployments
| Schema Deployments | Content and Media Transfers |
| --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Schema is stored in a Git repository. These are **deployed** between environments using a Git client or the Umbraco Cloud Portal. | Content and Media items are not stored in the Git repository. They must be **transferred** directly from the Umbraco backoffice using the **Add to Transfer Queue** option. Once queued, use the **Deploy Overview** in the Umbraco Backoffice to complete the transfer. |
Content editors do not need Umbraco Cloud Portal access. They can manage content through the backoffice, while developers handle schema deployments via Git.
### Deploy Schema
The source and target environments must be in sync before transferring content and media. Deploy the schema first to ensure consistency.
* [Deploy changes from Local to Cloud](/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/local-to-cloud.md)
* [Deploy changes between Cloud environments](/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/cloud-to-cloud.md)
* [Umbraco Forms on Cloud](/umbraco-cloud/expand-your-projects-capabilities/cloud-extensions/umbraco-forms-on-cloud.md)
### Transfer Items Between Environments
Content, Media, and Forms move between environments through the Umbraco backoffice. Items are transferred from left to right and restored from right to left.
* [Transfer Items](/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/content-transfer.md)
* [Restore Items](/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/restoring-content.md)
## [Deploy configuration](https://docs.umbraco.com/umbraco-deploy/getting-started/deploy-settings)
All configuration for Umbraco Deploy is stored in the `appSettings.json` file found at the root of your Umbraco website.
## Environment Restart
Some deployments can trigger an Umbraco Cloud environment to restart. The table below outlines which actions initiate a restart.
| Action: | Application Restart? |
| ----------------------------------- | -------------------- |
| Config file change | Yes |
| Schema deployment | No |
| File change (for example, CSS file) | No |
| Content or Media transfer | No |
### Manual Restart
From the Umbraco Cloud Portal, you can manually restart your environments.
Restart an environment
## Umbraco-cloud.json
The `umbraco-cloud.json` file defines deployment settings, identifies the current environment, and determines the next deployment target.
{% hint style="info" %}
The `name` attribute in the `umbraco-cloud.json` can be updated to clarify deployment destinations in the Workspaces dashboard.
{% endhint %}
***
---
# 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://docs.umbraco.com/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment.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.