You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Environments are a core part of your Umbraco Cloud project. This is where you develop, write, build, and eventually publish your website.
2
+
description: >-
3
+
Environments are a core part of your Umbraco Cloud project. This is where you
4
+
develop, write, build, and eventually publish your website.
3
5
---
4
6
5
7
# Environments
6
8
7
9
An Umbraco Cloud environment is defined as a _workspace_ and is also a Git repository. When you have more than one environments on your project, these environments act as branches of the main repository.
8
10
9
-
Umbraco Cloud uses a deployment model that relies on Git and other core technology. This gives you the option to move both content and structure files from one environment to another. Learn more in the [Deployment section](../deployment/README.md).
11
+
Umbraco Cloud uses a deployment model that relies on Git and other core technology. This gives you the option to move both content and structure files from one environment to another. Learn more in the [Deployment section](../deployment/).
10
12
11
13
You can have multiple environments in your Umbraco Cloud project, with two types available: **Mainline Environments** and **Flexible Environments**.
12
14
@@ -16,7 +18,7 @@ The image below shows a Cloud setup including two mainline environments and one
16
18
17
19
## Mainline Environments
18
20
19
-
A mainline environment serves as the root deployment pipeline, responsible for managing code and content flow. Each mainline environment is a part of the [left-to-right deployment workflow](../deployment/README.md).
21
+
A mainline environment serves as the root deployment pipeline, responsible for managing code and content flow. Each mainline environment is a part of the [left-to-right deployment workflow](../deployment/).
20
22
21
23
The **left-most mainline environment** is where you can connect to your local machine using Git. This environment is often called the Development environment.
22
24
@@ -36,63 +38,55 @@ Learn more about how this works in the [Flexible Environments](flexible-environm
Each environment on Umbraco Cloud has both a Git repository and a folder with your actual live site. The Git repository is what you clone down when you work with the project locally, and it's where your changes are pushed to.
71
48
72
49
The live site (`/site/wwwroot/`) contains the files used to show your website to the world. When pushing changes from your local machine, they are pushed to the Git repository (`/site/repository/`). When this finishes successfully, the changes are copied into the live site.
73
50
74
-
## Team Members
51
+
### Configuration files
52
+
53
+
An `appSettings.json` file holds all configurations for the Umbraco CMS project within the Cloud project. This file follows ASP.NET standards as they are tied to the Umbraco CMS installation.
54
+
55
+
It is possible to set up specific configurations for each environment:
56
+
57
+
1. Clone the `appSettings.json` file.
58
+
2. Rename it by adding the environment name: `appSettings.{EnvironmentAlias}.json`. 
59
+
60
+
The `EnvironmentAlias` is fetched from the Environment variable named `DOTNET_ENVIRONMENT`. This variable can be found in the Environment Variables section of Kudu on the environment. You can read more about ASP.NET Configuration in the official [Microsoft documentation](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-9.0).
61
+
62
+
{% hint style="info" %}
63
+
Make sure that when you start up the Umbraco Application, you load the correct JSON file as per the ASP.NET Configuration in the official [Microsoft documentation](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/configuration/?view=aspnetcore-9.0).
64
+
{% endhint %}
65
+
66
+
### Team Members
75
67
76
68
All the team members you add through the Umbraco Cloud Portal will also be added as backoffice users in your environments. You can also add users directly in the backoffice of your Umbraco Cloud environments. If you do this, the user will not have the option to deploy changes between the environments.
77
69
78
70
Read more about this and team member roles in the [Team Members](../set-up/project-settings/team-members/) article.
79
71
80
-
## SQL Database
72
+
###SQL Database
81
73
82
74
Each of your Umbraco Cloud environments has its own SQL Azure database. You have full access to the databases, and you can create custom tables as you'd expect from any other hosting provider.
83
75
84
76
Learn more about how to connect to your Umbraco Cloud databases in the [Database](../databases/) article.
85
77
86
-
## Power Tools (Kudu)
78
+
###Power Tools (Kudu)
87
79
88
80
Aside from viewing the files when cloning down the project to your local machine, you also have access to Kudu (Power Tools).
89
81
90
82
Kudu is a dashboard that allows you to browse, view, and edit all the files in your environments. We recommend using the tool _only_ when you are following one of our guides.
91
83
92
84
In the [Power Tools](../set-up/power-tools/) article, you can read more about how to access the dashboard, and how we recommend using it.
93
85
94
-
## Environment History
86
+
###Environment History
95
87
96
88
Each of your Umbraco Cloud environments has a Git repository and therefore also a Git history. We've made a simplified view of this Git history in the Cloud Portal. The **History** is found via the action menu available on each environment in the environments overview on your project.
97
89
98
90
In the History view, you'll be able to see what file changes have been made in the environment.
0 commit comments