Skip to content

Commit 29db9eb

Browse files
Sofie Toft Kristensengitbook-bot
authored andcommitted
GITBOOK-91: No subject
1 parent f949594 commit 29db9eb

File tree

2 files changed

+20
-8
lines changed

2 files changed

+20
-8
lines changed

umbraco-cloud/deployment/cloud-to-cloud.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ When your are Working in your Development environment, changes made through the
88

99
Changes made on your Cloud environments will show up in the Umbraco Cloud portal. You'll be able to see what files have been added/changed and who made the changes.
1010

11-
To deploy metadata changes from one Cloud environment to another, click the **'Deploy changes to ..'** button on the environment where the changes have been made. 
11+
To deploy metadata changes from one Cloud environment to another, click the **'Deploy changes to ..'** button on the environment where the changes have been made.
1212

1313
<figure><img src="../.gitbook/assets/image (39).png" alt=""><figcaption></figcaption></figure>
1414

@@ -22,7 +22,7 @@ Once it's done, the changes will be deployed to the next Cloud environment. If y
2222

2323
When you deploy, for example, from your Development environment to your Live environment, changes are made to the Live environment. These changes will then be merged back into the Development environment.
2424

25-
Here are the auto-magical steps Umbraco Cloud goes through when you hit the _"Deploy changes to .."_ button:
25+
Here are the automatic steps Umbraco Cloud goes through when you hit the _"Deploy changes to .."_ button:
2626

2727
* Before pushing your changes from the source environment, the engine running Umbraco Cloud - **Umbraco Deploy** - looks for changes in the repository on the target environment
2828
* If changes are found, Umbraco Deploy _merges_ the changes from the target environment into the repository on the source environment.
@@ -36,5 +36,3 @@ It is important to be aware of how deletions work between environments. Some del
3636
{% endhint %}
3737

3838
Refer to our troubleshooting documentation about [how to resolve collision errors](../troubleshooting/deployments/structure-error.md), if you should run into issues while deploying between your Umbraco Cloud environments.
39-
40-

umbraco-cloud/getting-started/flexible-environments.md

Lines changed: 18 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,22 +11,36 @@ hidden: true
1111
Beta feature: Some features might not be fully available.
1212
{% endhint %}
1313

14-
Flexible Environments allow users to create and manage an unlimited number of environments. 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.
14+
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.
1515

1616
{% hint style="info" %}
17-
Current limitations
17+
Limitations
1818

1919
* Only one flexible environment is available.
2020
* Flexible environments are only available to Projects paid with Invoices or Credits.
2121
* CI/CD Pipelines are not supported.
2222
{% endhint %}
2323

24-
With Flexible Environments, teams can create as many environments as needed, allowing for more efficient and tailored workflows.
24+
With Flexible Environments, teams can create environments as needed, allowing for more efficient and tailored workflows.
2525

2626
This feature enables:
2727

2828
* **Parallel development and testing**: Developers can create isolated environments for different features, bug fixes, or client-specific work without impacting the main development branch.
2929
* **Custom workflow orchestration**: Teams can define custom flows of code and content deployment rather than being restricted to a linear left-to-right approach.
3030
* **Easier hotfixes and feature releases**: Urgent fixes can be deployed directly without being blocked by unfinished work in other environments.
31+
* **Improved Content Management**: Content editors can create, test, and validate content changes without depending on a specific environment.
3132

32-
Improved Content Management: Content editors can create, test, and validate content changes without depending on the Development environment.
33+
## Project Prerequisites
34+
35+
Before you can add a Flexible environment to your project, the following prerequisites must be met:
36+
37+
* Uses Umbraco Version 10, 13, 14 or greater.
38+
* Uses Deploy Version Greater than 10.4.1, 13.3.0, 14.2.0 or greater.
39+
40+
{% hint style="info" %}
41+
Flexible Environments are not available on Heartcore projects.
42+
{% endhint %}
43+
44+
## Plans and Availability
45+
46+
<table><thead><tr><th width="117">Plan</th><th width="116" data-type="number">Environments</th><th width="167" data-type="checkbox">Flexible Environments</th><th>Environment Combinations Examples</th></tr></thead><tbody><tr><td>Starter</td><td>2</td><td>false</td><td><em>QA + Production</em></td></tr><tr><td>Standard</td><td>3</td><td>true</td><td><em>Flexible + QA + Production</em><br><em>Development + QA + Production</em></td></tr><tr><td>Professional</td><td>4</td><td>true</td><td><em>Flexible + Development + QA + Production</em></td></tr></tbody></table>

0 commit comments

Comments
 (0)