GITBOOK-2: Replace environment references from Set Up section

gitbook-bot · gitbook-bot · commit fb1fd845f028 · 2025-04-08T08:54:11.000Z
diff --git a/umbraco-cloud/.gitbook/assets/environments-overview-new.png b/umbraco-cloud/.gitbook/assets/environments-overview-new.png
diff --git a/umbraco-cloud/set-up/azure-blob-storage/connect-to-azure-storage-explorer.md b/umbraco-cloud/set-up/azure-blob-storage/connect-to-azure-storage-explorer.md
@@ -10,7 +10,7 @@ description: >-
 This article provides the steps you need, to connect to your Azure Blob Storage containers using Azure Storage Explorer.
 
 {% hint style="warning" %}
-We **strongly** recommend that you add all the media items to your Cloud environments through the backoffice. Clone your environment to your local machine to manage the files of your media library.
+It is **strongly** recommend that you add all the media items to your Cloud environments through the backoffice. Clone your environment to your local machine to manage the files of your media library.
 
 **Important**: If you upload your media files manually using this method, they will not be available in the backoffice.
 
@@ -19,7 +19,7 @@ All media needs to be added through the Umbraco backoffice.
 
 ## Getting the credentials
 
-The first thing to sort out, if you want to connect to the Azure Blob Storage container of your environment is the credentials.&#x20;
+The first thing to sort out, if you want to connect to the Azure Blob Storage container of your environment is the credentials.
 
 To find the connection details for your environment's Blob Storage, follow the steps below:
 
diff --git a/umbraco-cloud/set-up/going-live.md b/umbraco-cloud/set-up/going-live.md
@@ -20,7 +20,7 @@ Before adding a hostname, you need to update your DNS host domain registrar DNS
 
 ## [Deploy to Live](../deployment/cloud-to-cloud.md)
 
-The last step before your website goes live and is accessible to the public is to deploy it to the Live environment. When everything has been tested in your development environment or locally, you are ready to deploy the site to your live environment and make it public.
+The last step before your website goes live and is accessible to the public is to deploy it to the Live environment. When everything has been tested in the left-most mainline environment or locally, you are ready to deploy the site to your live environment and make it public.
 
 {% hint style="info" %}
 If you would like to keep track of what goes on with your website after it has gone live, you can set up a [Deployment Webhook](../deployment/deployment-webhook.md). This is a great way to keep an eye on your project and it works great with [Slack](https://slack.com/).
diff --git a/umbraco-cloud/set-up/media.md b/umbraco-cloud/set-up/media.md
@@ -15,7 +15,7 @@ To access the media files on your Umbraco Cloud project you can either:
 
 ## About Azure Blob Storage <a href="#about-azure-blob-storage" id="about-azure-blob-storage"></a>
 
-Azure Blob Storage is an external storage system, that the Umbraco Cloud service uses to store all media files on Umbraco Cloud projects.  To learn how you can connect to your Blob Storages, read the [Azure Blob Storage](azure-blob-storage/) article.
+Azure Blob Storage is an external storage system, that the Umbraco Cloud service uses to store all media files on Umbraco Cloud projects. To learn how you can connect to your Blob Storages, read the [Azure Blob Storage](azure-blob-storage/) article.
 
 ## Working with media locally
 
@@ -31,7 +31,7 @@ Each environment on your Umbraco Cloud project has a separate Azure Blob Storage
 
 When you deploy between two environments on your Umbraco Cloud project the media files will be copied from one storage to the other, depending on which environment is being transferred to and from.
 
-As an example, imagine that you are transferring new content changes from your Development environment to your Live environment. When you initiate the transfer, all media files from the Azure Blog Storage container connected to your Development environment will be copied and pasted into the container connected to your Live environment. Once all content changes have also been transferred, and the transfer is complete, your Media libraries on the two environments will now be in sync.
+As an example, imagine that you are transferring new content changes from your left-most mainline environment to your Live environment. When you initiate the transfer, all media files from the Azure Blob Storage container connected to your left-most mainline environment will be copied and pasted into the container connected to your Live environment. Once all content changes have also been transferred, and the transfer is complete, your Media libraries on the two environments will now be in sync.
 
 ## Media Folder
 
diff --git a/umbraco-cloud/set-up/project-settings/README.md b/umbraco-cloud/set-up/project-settings/README.md
@@ -14,7 +14,7 @@ The Environments section provides an overview of your project’s environments.
 * Open Kudu, and
 * Clone down the environment locally.
 
-![Environments Overview](../images/environments-new.png)
+![Environments Overview](../../.gitbook/assets/environments-overview-new.png)
 
 #### Environment error log
 
diff --git a/umbraco-cloud/set-up/project-settings/project-history.md b/umbraco-cloud/set-up/project-settings/project-history.md
@@ -27,12 +27,12 @@ For each activity you can see the following information:
 * When the activity ended
 * The status of the activity
 
-To get a detailed view of each history type on your project, click the info icon on the far right of the history activity.&#x20;
+To get a detailed view of each history type on your project, click the info icon on the far right of the history activity.
 
 If you click on the info icon for an automatic update, you will be redirected to an Upgrade Details page. On this page, you can see details about how the upgrade went.
 
 <figure><img src="../../.gitbook/assets/image (14) (1).png" alt=""><figcaption><p>Upgrade Details</p></figcaption></figure>
 
-For activities like adding and removing environments,  clicking on the info icon will show details of how the process went when adding/ removing the environment.
+For activities like adding and removing environments, clicking on the info icon will show details of how the process went when adding/removing the environment.
 
 <figure><img src="../../.gitbook/assets/image (15) (1).png" alt=""><figcaption><p>Adding environment details</p></figcaption></figure>
diff --git a/umbraco-cloud/set-up/project-settings/secrets-management.md b/umbraco-cloud/set-up/project-settings/secrets-management.md
@@ -7,11 +7,11 @@ description: >-
 
 # Secrets Management
 
-There are two ways to add secrets to your Cloud project, as an **Environment Secrets** or as a **Shared Secrets**.
+There are two ways to add secrets to your Cloud project, as an Environment Secrets or as a Shared Secrets.
 
-&#x20;**Environment Secrets** are intended to be utilized exclusively within a particular environment during the runtime of your Umbraco solution.
+Environment Secrets are intended to be utilized exclusively within a particular environment during the runtime of your Umbraco solution.
 
-**Shared Secrets** are utilized across all environments and will be seamlessly integrated into any new environment you create. Shared Secrets are particularly well-suited for safeguarding credentials necessary for project development, such as access to private NuGet feeds.
+Shared Secrets are utilized across all environments and will be seamlessly integrated into any new environment you create. Shared Secrets are particularly well-suited for safeguarding credentials necessary for project development, such as access to private NuGet feeds.
 
 {% hint style="warning" %}
 Utilizing environment-specific secrets for private NuGet feeds will result in the unsuccessful creation of new environments due to the unknown status of the secret. In such instances, **Shared Secrets** should be used.
@@ -38,7 +38,7 @@ When adding a secret to your environment it will restart.
 To add a secret to your environment follow these steps:
 
 1. Go to your Umbraco Cloud project
-2. Go to the settings section and go to Secret Management
+2. Go to the Settings section and go to Secret Management
 3. Choose either shared or environment secrets
 4. Choose the environment to add the secret and click Add secret
 5. Add the Key and the Value in the fields and click Add secret
@@ -139,7 +139,7 @@ The list consists of:
 * `SERVICEBUSCONNSTR_`
 * `EVENTHUBCONNSTR_`
 * `DOCDBCONNSTR_`
-* `REDISCACHECONNSTR_`	
+* `REDISCACHECONNSTR_`
 * `FILESHARESTORAGE_`
 
 {% hint style="info" %}
@@ -159,7 +159,6 @@ The following prefixes are allowed for Secrets on Umbraco Cloud:
 * `UMBRACO__AUTHORIZEDSERVICES__`
 * `UMBRACO__COMMERCE__`
 
-
 It is also possible to use Secrets to save API keys, Passwords, and ReChaptcha for all our Umbraco products on Umbraco Cloud.
 
 Do you have an existing or new secret that you want to add to a key vault that conflicts with the name restrictions?
diff --git a/umbraco-cloud/set-up/project-settings/team-members/README.md b/umbraco-cloud/set-up/project-settings/team-members/README.md
@@ -12,7 +12,7 @@ When adding a user, the default permission is _Read_ for each environment. You c
 
 ## Team Member User Permissions
 
-User Permissions for each environment can be set in the **Edit Team** page available from the **Settings** dropdown. User Permissions can be set per environment. For example, a user can have Write access on the Development environment and Read access on the Live environment.
+User Permissions for each environment can be set in the **Edit Team** page available from the **Settings** dropdown. User Permissions can be set per environment. For example, a user can have Write access on the left-most mainline environment and Read access on the Live environment.
 
 <figure><img src="../../team-members/images/Edit-Team.png" alt=""><figcaption></figcaption></figure>
 
diff --git a/umbraco-cloud/set-up/project-settings/umbraco-cicd/KnownLimitationsAndConsiderations.md b/umbraco-cloud/set-up/project-settings/umbraco-cicd/KnownLimitationsAndConsiderations.md
@@ -10,7 +10,7 @@ As we continue to gather insights from our users, there are some known limitatio
 
 **Workflow considerations**
 
-* To ensure smooth execution of the CI/CD Flow, it is recommended to make schema changes in the [leftmost environment](../../../deployment/README.md). Ideally, this means the local development environment. Schema changes include changes made to Document Types, Data Types, Templates, and the like. The intention behind this principle is to prevent conflicts that could potentially arise due to simultaneous modifications made in different environments.
+* To ensure smooth execution of the CI/CD Flow, it is recommended to make schema changes in the [left-most mainline environment](../../../deployment/). For example, the local development environment. Schema changes include changes made to Document Types, Data Types, Templates, and the like. The intention behind this principle is to prevent conflicts that could potentially arise due to simultaneous modifications made in different environments.
 
 **Additional Build Step**
 
@@ -33,4 +33,3 @@ As we continue to gather insights from our users, there are some known limitatio
 * **Casing Conflicts**: Be cautious of casing issues, such as having a README.md file created by Azure DevOps and a `Readme.md` file from the default Umbraco Cloud, as this can cause conflicts in the cloud Git repository.
 * **Documentation Alignment**: We are in the process of updating our documentation to align with standard Umbraco guidelines.
 * **Developer Experience**: Plans are underway to create Umbraco-specific Azure DevOps tasks and GitHub Actions to enhance the developer experience.
-
diff --git a/umbraco-cloud/set-up/project-settings/umbraco-cicd/README.md b/umbraco-cloud/set-up/project-settings/umbraco-cicd/README.md
@@ -34,7 +34,7 @@ The CI/CD process for Umbraco projects involves some key steps, from code develo
 2. **Customer code repository**: Changes are committed and pushed to a version control system like Git in the customer's own repository.
 3. **Customer pipeline**: The code is compiled and built. Tests can be run automatically in the associated pipeline to ensure code quality. Finally, the code is packaged into a zip file and prepared for deployment.
 4. **Umbraco Cloud API**: The customer pipeline uploads the source packed as a zip file to Umbraco Cloud API.
-5. **Umbraco cloud repository**: The deployments start which triggers the queueing of the build in Umbraco services. It then pushed the Umbraco Cloud repository to the left-most environment. And if a live environment, the website has been updated.
+5. **Umbraco cloud repository**: The deployments start which triggers the queueing of the build in Umbraco services. It then pushed the Umbraco Cloud repository to the left-most mainline environment. And if a live environment, the website has been updated.
 
 ![Basic overview](../../images/NewBasicFlow.png)
 
@@ -44,7 +44,7 @@ In a bit more detail the flow will look like this from a pipeline perspective.
 
 ## Next Steps: Dive into the Documentation
 
-To ensure you make the most of Umbraco CI/CD Flow, we suggest exploring the documentation further. Familiarizing yourself with the fundamentals is a good starting point, but delving deeper will enable you to fully harness its capabilities.&#x20;
+To ensure you make the most of Umbraco CI/CD Flow, we suggest exploring the documentation further. Familiarizing yourself with the fundamentals is a good starting point, but delving deeper will enable you to fully harness its capabilities.
 
 Here are three essential pages to get you started:
 
diff --git a/umbraco-cloud/set-up/project-settings/umbraco-cicd/Troubleshooting.md b/umbraco-cloud/set-up/project-settings/umbraco-cicd/Troubleshooting.md
@@ -12,9 +12,9 @@ To resolve this issue, remove the `RestorePackagesWithLockFile` to allow the dep
 
 ## cloud-sync
 
-### The projects left-most environment has changed
+### The projects left-most mainline environment has changed
 
-The mechanism to determine changes since the last deployment is not able to do so when the left-most environment has changed. This happens when you either add or remove the development environment. The [get diff endpoint](UmbracoCloudApi.md#get-deployment-diff) responds with status 409 and the following json payload:
+The mechanism to determine changes since the last deployment is not able to do so when the left-most mainline environment has changed. This happens when you either add or remove a mainline environment. The [get diff endpoint](UmbracoCloudApi.md#get-deployment-diff) responds with status 409 and the following json payload:
 
 ```json
 {
@@ -26,14 +26,14 @@ The mechanism to determine changes since the last deployment is not able to do s
 }
 ```
 
-You will need to _manually_ make sure that all latest changes on your left-most environment in cloud is also present in your local copy.
+You will need to _manually_ make sure that all latest changes on your left-most mainline environment in cloud is also present in your local copy.
 
 Once this is done you can run a new deployment, where you skip the cloud-sync step.
 
 * [Skip cloud-sync in GitHub](Troubleshooting.md#skip-cloud-sync-in-github)
 * [Skip cloud-sync in Azure DevOps](Troubleshooting.md#skip-cloud-sync-in-azure-devops)
 
-If you experience problems with your development environment not properly booting up after deployment, [read the Unable to determine environment by its {environment-id} guide](Troubleshooting.md#unable-to-determine-environment-by-its-environment-id).
+If you experience problems with your environment not properly booting up after deployment, [read the Unable to determine environment by its {environment-id} guide](Troubleshooting.md#unable-to-determine-environment-by-its-environment-id).
 
 ### “Apply Remote Changes” step is failing
 
@@ -159,7 +159,7 @@ In order to fix this issue, you need to use [KUDU](../../power-tools/) to remove
 1. Access KUDU on the "left-most" environment
 
 * If you only have one environment you want the live environment
-* If you have more than one environment, you want the development environment
+* If you have more than one environment, you want the left-most mainline environment
 
 3. Navigate to `site` > `locks` folder In there, there should be a file named `updating`
 4. Remove the `updating` file.
@@ -170,18 +170,18 @@ Once the marker file is removed, run your pipeline again.
 
 ### Unable to determine environment by its {environment-id}
 
-This happens when you use the CI/CD feature of Umbraco Cloud to deploy changes to your live environment, and later add a development environment. Your development environment will fail to boot up and will show the following error message:
+This happens when you use the CI/CD feature of Umbraco Cloud to deploy changes to your live environment, and later add a new Cloud environment. Your environment will fail to boot up and will show the following error message:
 
 ```
 “System.InvalidOperationException: Unable to determine environment by its {environment-id}”
 ```
 
-This issue arises because the development environment is missing in the local umbraco-cloud.json file. To resolve this issue, follow these steps:
+This issue arises because the environment is missing in the local umbraco-cloud.json file. To resolve this issue, follow these steps:
 
 1. Navigate to Kudu in your Live environment
 2. Select “Debug console” and choose “CMD”.
 3. Find the umbraco-cloud.json file. Path to this file may vary depending on your setup, but the default location on cloud is C:\home\site\repository\src\UmbracoProject
 4. Click ‘edit’ on the file and copy all its content. This content is consistent across environments, so it’s safe to do so.
 5. Paste the copied content into the umbraco-cloud.json file in your local project and push the changes.
 
-After completing these steps, your development environment should be correctly registered across all environments, allowing you to continue your work without any issues.
+After completing these steps, your left-most mainline environment should be correctly registered across all environments, allowing you to continue your work without any issues.
diff --git a/umbraco-cloud/set-up/project-settings/umbraco-cicd/UmbracoCloudApi.md b/umbraco-cloud/set-up/project-settings/umbraco-cicd/UmbracoCloudApi.md
@@ -337,10 +337,6 @@ fi
 
 The API response will vary based on whether or not there are changes to report. If no changes are detected, you'll receive an HTTP 204 No Content status. On the other hand, if there are changes, the API will return an HTTP 200 OK status along with a git-patch file as the content. This git-patch file can then be applied to your local repository to sync it with the changes.
 
-### Promote Deployment
-
-Currently, the feature to transition from a development environment to staging or live, and from staging to live, is pending implementation. In the meantime, you can manage these transitions manually through the [Umbraco Cloud Portal](https://www.s1.umbraco.io/projects) \[link to relevant page in docs.umbraco.com, e.g. the section “Utilizing the Pipeline” of the new page “How To Configure A Sample CI|CD Pipeline”]..
-
 ### Possible errors
 
 When interacting with the Umbraco Cloud API, you may encounter various HTTP status codes that indicate the success or failure of your API request. Below is a table summarizing the possible status codes, their corresponding errors, and basic root causes to guide your troubleshooting:
diff --git a/umbraco-cloud/set-up/ready-to-set-up-your-project.md b/umbraco-cloud/set-up/ready-to-set-up-your-project.md
