From 2bb3f80c5b642f178e229c088c1f005af89f6756 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 1 Aug 2025 16:57:04 +0000 Subject: [PATCH 1/3] Initial plan From 5deb0a25a4a909e51fe9f39de1f5e58c13dbacd3 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 1 Aug 2025 17:12:14 +0000 Subject: [PATCH 2/3] Consolidate playground documentation pages and add redirect Co-authored-by: lionello <591860+lionello@users.noreply.github.com> --- docs/concepts/defang-playground.md | 20 +++++++++++++++++++- docs/providers/playground.md | 20 +++----------------- docusaurus.config.js | 4 ++++ 3 files changed, 26 insertions(+), 18 deletions(-) diff --git a/docs/concepts/defang-playground.md b/docs/concepts/defang-playground.md index 4a7e4f06ae..5c3cf1973c 100644 --- a/docs/concepts/defang-playground.md +++ b/docs/concepts/defang-playground.md @@ -8,12 +8,22 @@ sidebar_position: 00 Defang aims to make it easier to deploy your services to the cloud. Specifically, Defang's goal is to make it easier to deploy your workloads to your *own* cloud accounts. We refer to this as bring-your-own-cloud (BYOC) which you can read about in more depth [here](./defang-byoc). We also provide Defang Playground, but it is only intended for non-production workloads so you can get a feel for how Defang works. -Defang Playground is a free tier that allows you to deploy services to a Defang-hosted cloud account without needing to manage your own. It is intended for non-production workloads only. +Defang Playground is a free tier that allows you to deploy services to a Defang-hosted cloud account without needing to manage your own. It is intended for non-production workloads only. The Playground is a great way to get started with Defang. You can even use [1-Click Deploy](/docs/tutorials/using-one-click-deploy) to try it out quickly or you can get started with the [Defang CLI](/docs/getting-started). :::warning Please note that the Defang Playground is intended for testing/learning purposes only. The environment may be reset at any time. Do not run production workloads in Defang Playground. ::: +:::info +The Playground allows only 1 deployed project at a time. Use the CLI `defang down` command to tear down a project before deploying a new one. +::: + +## Overview + +Overall, the Defang Playground is very similar to deploying to your own cloud account. The Playground runs on a Defang-managed AWS account, so you can expect it to work similarly to deploying to [AWS](../providers/aws/aws.md). + +This page highlights architectural considerations when deploying to the Playground and any differences you might encounter when deploying to the Playground versus deploying to your own cloud account. + ## Limitations There are a few limitations to Defang Playground. These limitations are in place to ensure that Defang Playground is only used for non-production workloads. If you are interested in running production workloads, you should use Defang BYOC. @@ -29,3 +39,11 @@ When you deploy a service to Defang Playground, it will be assigned a domain und * CPUs: 2 * Memory: 1GiB * Replicas: 1 + +### Managed services + +In essence, the Playground does not support any [managed storage](./managed-storage) services, ie. `x-defang-postgres` and `x-defang-redis` are ignored when deploying to the Playground. You can however run both Postgres and Redis as regular container services for testing purposes. + +### Managed LLMs + +Defang offers integration with managed, cloud-native large language model services with the `x-defang-llm` service extension when deploying to your own cloud account with BYOC. This extension is supported in the Defang Playground with one caveat: your MODEL (model ID) will be limited to a default model chosen by Defang. diff --git a/docs/providers/playground.md b/docs/providers/playground.md index 5f6e3d60a3..30f359b3f8 100644 --- a/docs/providers/playground.md +++ b/docs/providers/playground.md @@ -4,22 +4,8 @@ description: The Defang Playground is a free tier that allows you to experiment sidebar_position: 0000 --- -The Defang Playground is a free deployment provider that allows you to experiment with Defang. The Playground is a shared environment that should not be used to run production workloads. The Playground is a great way to get started with Defang. You can even use [1-Click Deploy](/docs/tutorials/using-one-click-deploy) to try it out quickly or you can get started with the [Defang CLI](/docs/getting-started). +# Playground -This page highlights architectural considerations when deploying to the Playground and any differences you might encounter when deploying to the Playground versus deploying to your own cloud account. +This page has been moved to the [Concepts section](/docs/concepts/defang-playground). -:::info -The Playground allows only 1 deployed project at a time. Use the CLI `defang down` command to tear down a project before deploying a new one. -::: - -## Overview - -Overall, the Defang Playground is very similar to deploying to your own cloud account. The Playground runs on a Defang-managed AWS account, so you can expect it to work similarly to deploying to [AWS](./aws/aws.md). - -### Managed services - -In essence, the Playground does not support any [managed storage](../concepts/managed-storage) services, ie. `x-defang-postgres` and `x-defang-redis` are ignored when deploying to the Playground. You can however run both Postgres and Redis as regular container services for testing purposes. - -### Managed LLMs - -Defang offers integration with managed, cloud-native large language model services with the `x-defang-llm` service extension when deploying to your own cloud account with BYOC. This extension is supported in the Defang Playground with one caveat: your MODEL (model ID) will be limited to a default model chosen by Defang. +You will be automatically redirected to the new location. diff --git a/docusaurus.config.js b/docusaurus.config.js index 28091c5528..1f6a8388ce 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -13,6 +13,10 @@ const redirects = [ from: '/docs/faq', to: '/docs/faq/warnings-errors', }, + { + from: '/docs/providers/playground', + to: '/docs/concepts/defang-playground', + }, // Blog slugs to filename redirects { from: '/blog/announcement', to: '/blog/2023/06/29/Announcing-the-Private-Beta-for-the-DOP' }, { from: '/blog/announcing-defang-public-beta', to: '/blog/2024/02/12/announcing-defang-public-beta' }, From a4be7e5e2114b788e8deb1f2517aef6fc738689e Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 24 Nov 2025 19:47:32 +0000 Subject: [PATCH 3/3] Update playground documentation to reflect GCP and AWS deployment Co-authored-by: raphaeltm <910895+raphaeltm@users.noreply.github.com> --- docs/concepts/defang-playground.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/defang-playground.md b/docs/concepts/defang-playground.md index 5c3cf1973c..4e11ee559b 100644 --- a/docs/concepts/defang-playground.md +++ b/docs/concepts/defang-playground.md @@ -20,7 +20,7 @@ The Playground allows only 1 deployed project at a time. Use the CLI `defang dow ## Overview -Overall, the Defang Playground is very similar to deploying to your own cloud account. The Playground runs on a Defang-managed AWS account, so you can expect it to work similarly to deploying to [AWS](../providers/aws/aws.md). +Overall, the Defang Playground is very similar to deploying to your own cloud account. The Playground runs on Defang-managed GCP and AWS accounts, so you can expect it to work similarly to deploying to your own cloud. This page highlights architectural considerations when deploying to the Playground and any differences you might encounter when deploying to the Playground versus deploying to your own cloud account.