Skip to content

A few pointers to config transforms, more specifically setting up rewrites. #7346

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Sep 3, 2025
Merged

A few pointers to config transforms, more specifically setting up rewrites. #7346

Show file tree
Hide file tree
Changes from 4 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
118df9e
Add a few pointers to config transform section
andersreus Aug 27, 2025
f018d51
Merge branch 'umbraco:main' into main
andersreus Aug 27, 2025
329e285
Updates to troubleshooting page on ci/cd
andersreus Aug 27, 2025
919e769
Merge remote-tracking branch 'origin/main'
andersreus Aug 27, 2025
6f9161f
Update umbraco-cloud/build-and-customize-your-solution/handle-deploym…
eshanrnh Aug 27, 2025
1419894
Small updates
sofietoft Sep 1, 2025
8c274de
Update umbraco-cloud/build-and-customize-your-solution/set-up-your-pr…
sofietoft Sep 3, 2025
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
9 changes: 8 additions & 1 deletion ...ur-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,14 @@

For GitHub, see the [Skip cloud-sync in GitHub](troubleshooting.md#skip-cloud-sync-in-github) section.

With a few clicks you can manually trigger a pipeline to run without the cloud-sync:
Navigate to your azure-release-pipeline.yaml and comment out 35 and 36. More specifically these two lines:

Check warning on line 79 in umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[UmbracoDocs.Brands] Use 'Azure' instead of 'azure' for brand consistency.

Raw Output:
{"message": "[UmbracoDocs.Brands] Use 'Azure' instead of 'azure' for brand consistency.", "location": {"path": "umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md", "range": {"start": {"line": 79, "column": 18}}}, "severity": "WARNING"}
Copy link
Contributor

@sofietoft sofietoft Aug 27, 2025

Choose a reason for hiding this comment

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

Please but code tags around file names 🙏

Suggested change
Navigate to your azure-release-pipeline.yaml and comment out 35 and 36. More specifically these two lines:
Navigate to your `azure-release-pipeline.yaml` and comment out the following lines:

```sh
dependsOn: cloudSyncStage
condition: in(dependencies.cloudSyncStage.result, 'Succeeded', 'Skipped')
```

Trigger a code deployment and make sure to uncheck the "Umbraco Cloud Sync" stage as mentioned below.
~~With a few clicks you can manually trigger a pipeline to run without the cloud-sync:~~

1. Ensure that your Azure DevOps repository is up to date with any changes in your Umbraco Cloud environment.
2. Find the pipeline in Azure DevOps.
Expand Down
4 changes: 4 additions & 0 deletions ...stomize-your-solution/set-up-your-project/project-settings/config-transforms.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,8 @@

Create this file in your local project clone to ensure it's added to the repository.

{% hint style="info" %} If you don't have a web.config you will need to create one locally as well. {% endhint %}

When the file is deployed to the Live environment, the transforms will be applied to the `Web.config` file in the `Root` of your project. In the case that you have mutliple mainline environments, the `Web.Production.config` will **only** transform the `Web.config` on the Live environment.

For each deployment, the Umbraco Cloud engine searches for all of the `.{environment}.config` files in your site and apply the transforms.
Expand Down Expand Up @@ -93,6 +95,8 @@

This config transform will add a `<rule>` to `<system.webServer><rewrite><rules>`. The `xdt:Transform` attribute is used to tell the system what to transform. In this case, the value is `Insert`, which means it will add the section if it's not already in the config file.

If you don't have the `<rewrite>` and `<rules>` section in your `web.config` file, you can add the attribute `xdt:Transform="InsertIfMissing"` to those two section in the transform file and they will then get applied to the `web.config`.

Check warning on line 98 in umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/config-transforms.md

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[UmbracoDocs.SentenceLength] Write shorter sentences (less than 25 words). For content inside note or warning blocks, add blank lines around the content.

Raw Output:
{"message": "[UmbracoDocs.SentenceLength] Write shorter sentences (less than 25 words). For content inside note or warning blocks, add blank lines around the content.", "location": {"path": "umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/config-transforms.md", "range": {"start": {"line": 98, "column": 1}}}, "severity": "WARNING"}

## appsettings.json transforms

On Umbraco Cloud, projects come with an **appsettings.json** file for each of your different environments.
Expand Down
Loading