|
1 | 1 | # Repositories in a Cloud Project |
2 | 2 |
|
3 | | -Each Umbraco Cloud project can have multiple environments: Development, Staging, and Live depending on your Cloud project plan. Each environment has its own git repository that is hosted on Umbraco’s Cloud platform. |
| 3 | +Each Umbraco Cloud project can have multiple environments: Mainline and Flexible Environments. Each environment has its own git repository that is hosted on Umbraco’s Cloud platform. |
4 | 4 |
|
5 | 5 | {% hint style="info" %} |
6 | | -Umbraco Cloud repositories are _only_ deployment repositories and should not be used as source code repositories. |
| 6 | +Umbraco Cloud repositories are only deployment repositories and should not be used as source code repositories. |
7 | 7 | {% endhint %} |
8 | 8 |
|
9 | 9 | Ideally, your Umbraco Cloud setup should look like this: |
@@ -31,42 +31,40 @@ You need to put your custom code in a different source control repository of you |
31 | 31 | {% endtab %} |
32 | 32 | {% endtabs %} |
33 | 33 |
|
34 | | -## A Git Umbraco Cloud source control repository with the locally cloned Umbraco project |
| 34 | +## A source control repository with the locally cloned Umbraco project |
35 | 35 |
|
36 | | -We recommend creating a Cloud project with at least two environments: a Development environment and a Live environment. To work with a local copy of your site, you then clone down the Development environment using the **Clone project** option from the Cloud Portal and start building your website locally. This repository is different from your source control repository. |
| 36 | +We recommend creating a Cloud project with at least two environments: a Live environment including one extra mainline environment. Work with a local copy of the site by cloning down the left-most environment. This repository is different from your source control repository. |
37 | 37 |
|
38 | | -Once you're happy with the results or wish to see how your website has progressed, you push the changes back to the Development environment. If everything is working as expected you then deploy your changes to the Live environment. |
| 38 | +Once you're happy with the results or wish to see how your website has progressed, you push the changes back to the Cloud. If everything is working as expected, deploy your changes to the Live environment. |
39 | 39 |
|
40 | 40 | {% tabs %} |
41 | 41 | {% tab title="Umbraco 10+" %} |
42 | | -#### Code Deployment Summary |
| 42 | +### Code Deployment Summary |
43 | 43 |
|
44 | 44 |  |
45 | 45 |
|
46 | 46 | In the above diagram, the Umbraco Git repository contains the source code of a class library CS project. |
47 | 47 |
|
48 | 48 | With this setup, once you commit your code in the Umbraco Cloud Git repository, your C# source code is built by Umbraco Cloud and then deployed to the `wwwroot` folder. |
49 | 49 |
|
50 | | -#### Disadvantages of using an Umbraco Cloud Project repository as a source code repository |
| 50 | +### Disadvantages of using an Umbraco Cloud Project repository as a source code repository |
51 | 51 |
|
52 | 52 | * We only guarantee to maintain and keep the `master` branch. If there are any other branches, they might be removed without any notification causing data loss. |
53 | 53 | * You will need to commit your frontend artifacts as the build pipeline only builds dlls from your C# code. |
54 | 54 | {% endtab %} |
55 | 55 |
|
56 | 56 | {% tab title="Legacy Umbraco 7 and 8" %} |
57 | | -#### Code Deployment Summary |
| 57 | +### Code Deployment Summary |
58 | 58 |
|
59 | 59 | <figure><img src="../.gitbook/assets/UCP_v8.png" alt=""><figcaption><p>Umbraco cloud overview Legacy versions</p></figcaption></figure> |
60 | 60 |
|
61 | 61 | In the above diagram, the external git repository contains the source code of a class library CS project, if you had a class library project that was used in your Cloud project. |
62 | 62 |
|
63 | 63 | With this setup, you commit your changes twice. Once to commit your code in your source control and the other commit to the Umbraco Cloud Git repository to deploy your website. Your source code is not hosted on Umbraco Cloud but only your cloned project will be in the Umbraco Cloud Git Repository. Your code is built and compiled into the cloned project and then pushed to Umbraco Cloud. Thus updating the site with your latest code changes. |
64 | 64 |
|
65 | | -#### Disadvantages of using an Umbraco Cloud Project repository as a source code repository |
| 65 | +### Disadvantages of using an Umbraco Cloud Project repository as a source code repository |
66 | 66 |
|
67 | 67 | * We only guarantee to maintain and keep the `master` branch. If there are any other branches, they might be removed without any notification causing data loss. |
68 | 68 | * You will always need to commit your dll files. |
69 | 69 | {% endtab %} |
70 | 70 | {% endtabs %} |
71 | | - |
72 | | -## |
0 commit comments