Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion umbraco-cloud/SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,6 @@

## Deployments

* [Streamline Your Deployments](deployment/streamline-your-deployments.md)
* [Deployment](deployment/README.md)
* [Deploying between environments](deployment/cloud-to-cloud.md)
* [Transferring Content, Media, Members, and Forms](deployment/content-transfer.md)
Expand Down
27 changes: 0 additions & 27 deletions umbraco-cloud/deployment/streamline-your-deployments.md

This file was deleted.

32 changes: 21 additions & 11 deletions umbraco-cloud/getting-started/flexible-environments.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,15 +11,13 @@ hidden: true
Beta feature: Some features might not be fully available.
{% endhint %}

Flexible Environments allow users to create and manage environments outside the regular left-to-right deployment flow. This enhancement provides greater flexibility in orchestrating both code and content workflows, empowering developers and content editors to work in a way that best suits their needs.
Flexible Environments allow users to create and manage environments outside the regular left-to-right deployment flow. This enhancement provides flexibility in orchestrating code and content workflows, empowering developers and content editors to work in a way that best suits their needs.

{% hint style="info" %}
Limitations
While the mainline environments use a horizontal deployment flow, flexible environments work differently. A flexible environment is added to an existing mainline environment and only deploys to and from that environment. Get an overview of the different types of environments in the [Environments](environments.md) article.

* Only one flexible environment is available.
* Flexible environments are only available to Projects paid with Invoices or Credits.
* CI/CD Pipelines are not supported.
{% endhint %}
![A Cloud project set up with two mainline environments and one flexible environment](images/cloud-environments.png)

The image above shows a project setup including two mainline environments and one flexible environment attached to the left-most mainline environment.

With Flexible Environments, teams can create environments as needed, allowing for more efficient and tailored workflows.

Expand All @@ -30,16 +28,28 @@ This feature enables:
* **Easier hotfixes and feature releases**: Urgent fixes can be deployed directly without being blocked by unfinished work in other environments.
* **Improved Content Management**: Content editors can create, test, and validate content changes without depending on a specific environment.

## How it works

* A flexible environment is added and connected to a single mainline environment.
* Developers can develop and build features in the flexible environment without affecting the mainline environment.
* Once a feature is complete, it can be merged back into the mainline environment and become part of regular deployment flow.
* When changes are made to the mainline environment, they must be pulled into the flexible environment before changes can be pushed.

Learn more about the deployment process in the [Deployments](../deployment/README.md) section.

## Project Prerequisites

Before you can add a Flexible environment to your project, the following prerequisites must be met:

* Uses Umbraco Version 10, 13, 14 or greater.
* Uses Umbraco Version 10 or greater.
* Uses Deploy Version Greater than 10.4.1, 13.3.0, 14.2.0 or greater.

{% hint style="info" %}
Flexible Environments are not available on Heartcore projects.
{% endhint %}
### Limitations

* Only one flexible environment is available.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here, one is spelled out, and on line 20, it's in numbers. I prefer the spelled-out version since it's more formal. But you can choose either one and maintain consistency in the article.

* Flexible environments are available only for projects paid with invoices or credits.
* CI/CD Pipelines are not supported.
* Flexible Environments are not available for Heartcore projects.

## Plans and Availability

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.