From e04a39da301700fe26deec02ed1e7c85379c3ce8 Mon Sep 17 00:00:00 2001 From: Kemi-Elizabeth <97071326+Kemi-Elizabeth@users.noreply.github.com> Date: Tue, 4 Nov 2025 12:50:07 +0000 Subject: [PATCH 1/4] feat: updates to dg2 and node.js Updated registry.json and dg2 docs --- shared/data/registry.json | 1 + .../dedicated-environments/dedicated-gen-2/development.md | 6 ++++++ 2 files changed, 7 insertions(+) diff --git a/shared/data/registry.json b/shared/data/registry.json index 6e3be0986d..209d731aa2 100644 --- a/shared/data/registry.json +++ b/shared/data/registry.json @@ -681,6 +681,7 @@ }, "versions-dedicated-gen-2": { "supported": [ + "22", "20", "19" ], diff --git a/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md b/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md index d408cc7bd3..7a09d9c6c5 100644 --- a/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md +++ b/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md @@ -53,6 +53,12 @@ When deploying to the Dedicated Gen 2 cluster the process is slightly different - The deploy hook is run on one, and only one, of the three servers. - The cluster is opened to allow new requests. +{{< note title="info" theme="Note" >}} + +Note that hooks still run without containers. For example, [commands like `pre_start`](/create-apps/app-reference/single-runtime-image.md#web-commands) and other hooks run directly on the app docroot or worker service. + +{{< /note >}} + The deploy usually takes approximately 30-90 seconds, although that is dependent on how your deploy hook has been configured. During the deploy process the cluster is unavailable. All Dedicated Gen 2 instances are fronted by the Fastly Content Delivery Network (CDN) unless you decide to bring your own CDN. You can also decide that you'd rather not use Fastly. Fastly can be configured to allow a “grace period”, meaning that requests to the origin that fail are served from the existing cache, even if that cache item is stale. We configure a default grace period that is longer than a typical deployment, and can extend that time upon request. That means anonymous users should see no interruption in service at all. Authenticated traffic that can’t be served by the CDN still sees a brief interruption. From bcec587121f4b248124bc63b9ef6c675146851fc Mon Sep 17 00:00:00 2001 From: Kemi-Elizabeth <97071326+Kemi-Elizabeth@users.noreply.github.com> Date: Tue, 4 Nov 2025 13:02:26 +0000 Subject: [PATCH 2/4] feat: added vale filter vale didn't like docroot so included filter --- .../src/dedicated-environments/dedicated-gen-2/development.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md b/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md index 7a09d9c6c5..88806b81b5 100644 --- a/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md +++ b/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md @@ -52,13 +52,13 @@ When deploying to the Dedicated Gen 2 cluster the process is slightly different - The application image on all three servers is replaced with the new image. - The deploy hook is run on one, and only one, of the three servers. - The cluster is opened to allow new requests. - + {{< note title="info" theme="Note" >}} Note that hooks still run without containers. For example, [commands like `pre_start`](/create-apps/app-reference/single-runtime-image.md#web-commands) and other hooks run directly on the app docroot or worker service. {{< /note >}} - + The deploy usually takes approximately 30-90 seconds, although that is dependent on how your deploy hook has been configured. During the deploy process the cluster is unavailable. All Dedicated Gen 2 instances are fronted by the Fastly Content Delivery Network (CDN) unless you decide to bring your own CDN. You can also decide that you'd rather not use Fastly. Fastly can be configured to allow a “grace period”, meaning that requests to the origin that fail are served from the existing cache, even if that cache item is stale. We configure a default grace period that is longer than a typical deployment, and can extend that time upon request. That means anonymous users should see no interruption in service at all. Authenticated traffic that can’t be served by the CDN still sees a brief interruption. From 94679863b53497a83171e171f9a2dc1bca0c85d0 Mon Sep 17 00:00:00 2001 From: Kemi-Elizabeth <97071326+Kemi-Elizabeth@users.noreply.github.com> Date: Tue, 4 Nov 2025 13:22:04 +0000 Subject: [PATCH 3/4] feat: changed note changed note style --- .../src/dedicated-environments/dedicated-gen-2/development.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md b/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md index 88806b81b5..58c1e9c296 100644 --- a/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md +++ b/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md @@ -53,7 +53,7 @@ When deploying to the Dedicated Gen 2 cluster the process is slightly different - The deploy hook is run on one, and only one, of the three servers. - The cluster is opened to allow new requests. -{{< note title="info" theme="Note" >}} +{{< note title="note" theme="Note" >}} Note that hooks still run without containers. For example, [commands like `pre_start`](/create-apps/app-reference/single-runtime-image.md#web-commands) and other hooks run directly on the app docroot or worker service. From 4c7e08ce1547c6719f7af90dee8a3451bbf38781 Mon Sep 17 00:00:00 2001 From: Kemi-Elizabeth <97071326+Kemi-Elizabeth@users.noreply.github.com> Date: Tue, 4 Nov 2025 13:33:07 +0000 Subject: [PATCH 4/4] feat: capitalised note title capitalised note title --- .../src/dedicated-environments/dedicated-gen-2/development.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md b/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md index 58c1e9c296..b5f7ec7977 100644 --- a/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md +++ b/sites/platform/src/dedicated-environments/dedicated-gen-2/development.md @@ -53,7 +53,7 @@ When deploying to the Dedicated Gen 2 cluster the process is slightly different - The deploy hook is run on one, and only one, of the three servers. - The cluster is opened to allow new requests. -{{< note title="note" theme="Note" >}} +{{< note title="Note" theme="Note" >}} Note that hooks still run without containers. For example, [commands like `pre_start`](/create-apps/app-reference/single-runtime-image.md#web-commands) and other hooks run directly on the app docroot or worker service.