From 094251c65ea49398e41562d2558c5389b912c1b4 Mon Sep 17 00:00:00 2001 From: Florian Margaine Date: Fri, 21 Nov 2025 15:01:54 +0100 Subject: [PATCH] {all} is specific to an environment, not project when we introduced support for custom domains on development environments, the scope of {all} became reduced to the environment as well, not per project anymore. --- sites/platform/src/define-routes/_index.md | 6 +++--- sites/upsun/src/define-routes/_index.md | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/sites/platform/src/define-routes/_index.md b/sites/platform/src/define-routes/_index.md index 62372f8b40..5b4b3c6202 100644 --- a/sites/platform/src/define-routes/_index.md +++ b/sites/platform/src/define-routes/_index.md @@ -217,10 +217,10 @@ https://example.com.feature-t6dnbai-abcdef1234567.us-2.{{< vendor/urlraw "hostna ### `{all}` -You can also set up multiple domains for a single project. +You can also set up multiple domains for a single environment. To define rules for all of them, use `{all}` in your template. -Say you have both `example.com` and `example.net` as domains in a project. +Say you have both `example.com` and `example.net` as domains on an environment. You can then define the following routes: ```yaml {configFile="routes"} @@ -239,7 +239,7 @@ your app runs at both `https://example.com` and `https://example.net`. The second route means that `https://www.example.com` redirects to `https://example.com` _and_ `https://www.example.net` redirects to `https://example.net`. -If your project has no domains or only one, `{all}` behaves exactly like `{default}`. +If your environment has no domains or only one, `{all}` behaves exactly like `{default}`. If you have two routes sharing the same HTTP scheme, domain, and path and the first route is using `{default}` and the second is using `{all}`, diff --git a/sites/upsun/src/define-routes/_index.md b/sites/upsun/src/define-routes/_index.md index 5827d73aec..e1ca332825 100644 --- a/sites/upsun/src/define-routes/_index.md +++ b/sites/upsun/src/define-routes/_index.md @@ -186,10 +186,10 @@ Note that the `example.com` prefix isn't part of the generated URL. ### `{all}` -You can also set up multiple domains for a single project. +You can also set up multiple domains for a single environment. To define rules for all of them, use `{all}` in your template. -Say you have both `example.com` and `example.net` as domains in a project. +Say you have both `example.com` and `example.net` as domains on an environment. You can then define the following routes: ```yaml {configFile="routes"} @@ -209,7 +209,7 @@ your app runs at both `https://example.com` and `https://example.net`. The second route means that `https://www.example.com` redirects to `https://example.com` _and_ `https://www.example.net` redirects to `https://example.net`. -If your project has no domains or only one, `{all}` behaves exactly like `{default}`. +If your environment has no domains or only one, `{all}` behaves exactly like `{default}`. If you have two routes sharing the same HTTP scheme, domain, and path and the first route is using `{default}` and the second is using `{all}`,