diff --git a/docs/concepts/accounts.md b/docs/concepts/accounts.md index 97f6ce15f0..339ff7b311 100644 --- a/docs/concepts/accounts.md +++ b/docs/concepts/accounts.md @@ -7,7 +7,7 @@ description: How accounts are organized in Defang. Below, we will cover account creation with Defang, and how resources are organized within a cloud environment using your account info. -Defang requires an account so we can organize your resources and provide you with a way to manage them. We also use your account to authenticate you when you interact with [Defang Playground](./defang-playground.md) and the [Defang Portal](./portal.md). Billing and payment information is also associated with your account. +Defang requires an account so we can organize your resources and provide you with a way to manage them. We also use your account to authenticate you when you interact with the [Defang Portal](./portal.md). Billing and payment information is also associated with your account. ## Creating an Account @@ -34,7 +34,7 @@ For more information, see [Workspaces](./workspaces.md). Your GitHub username will be used as your Defang username. Your Defang username is used to group all your [services](/docs/concepts/services) and generate domains for your services with the following structure: ``` ----.prod1.defang.dev +--...defang.app ``` For more about domain structures, see our [Domains](/docs/concepts/domains#structure) page. diff --git a/docs/concepts/configuration.md b/docs/concepts/configuration.md index c89d2fe516..9b519ac2c2 100644 --- a/docs/concepts/configuration.md +++ b/docs/concepts/configuration.md @@ -107,7 +107,6 @@ Please note that while Defang supports setting sensitive config, it does not sup | Provider | Config Support | |----------------|:--------------:| -| Playground | ✅ | | AWS | ✅ | | DigitalOcean | ✅ | | GCP | ✅ | diff --git a/docs/concepts/defang-byoc.md b/docs/concepts/defang-byoc.md index e1043bedcc..f44b436ff9 100644 --- a/docs/concepts/defang-byoc.md +++ b/docs/concepts/defang-byoc.md @@ -5,7 +5,7 @@ description: Defang allows you deploy services, defined as containers, to your o # Defang BYOC -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). 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 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). Defang provisions and configures the necessary native managed services from your cloud provider to get your services up and running. For example, on AWS, Defang will configure an [ALB](https://aws.amazon.com/elasticloadbalancing/application-load-balancer/), set up [ECR](https://aws.amazon.com/ecr/), configure [CloudWatch](https://aws.amazon.com/cloudwatch/?nc2=type_a), and run your service on [ECS](https://aws.amazon.com/ecs/?nc2=type_a) and more. The following lists the existing and planned support for cloud providers. @@ -19,8 +19,7 @@ Defang does run the Defang build service to build your container images, which t The Defang CLI can be configured to deploy to a cloud provider either by using the `--provider` flag or by setting the `DEFANG_PROVIDER` environment variable. For example: ```bash -# Supported provider values: auto, aws, defang, digitalocean -# Default is auto, which deploys to the Defang Playground but warns if it detects cloud credentials +# Supported provider values: auto, aws, digitalocean $ defang compose up --provider=aws # or $ export DEFANG_PROVIDER=digitalocean diff --git a/docs/concepts/defang-playground.md b/docs/concepts/defang-playground.md deleted file mode 100644 index 99353c393d..0000000000 --- a/docs/concepts/defang-playground.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Defang Playground -description: Defang Playground allows you to get a feel for how Defang works without running production workloads in your own cloud accounts. ---- - -# Defang Playground - -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. - -:::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. -::: - -## 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. - -### No Apex Domain Support - -When you deploy a service to Defang Playground, it will be assigned a domain under the `defang.dev` domain. We do not support pointing your own apex domains to Defang Playground services, but you can use subdomains. - -### Max Resources - -* Projects: 1 -* Services: 4 -* CPUs: 2 -* Memory: 1GiB -* Replicas: 1 diff --git a/docs/concepts/deployments.md b/docs/concepts/deployments.md index 0a01288d3d..19eef5f78a 100644 --- a/docs/concepts/deployments.md +++ b/docs/concepts/deployments.md @@ -5,7 +5,7 @@ description: Defang will build your services in the cloud and manage the deploym # Deployment -When you deploy using Defang, whether it's with `defang compose up` with a [Compose file](./compose.md) or using a [Pulumi program](./pulumi.md), Defang will build your services in the cloud and manage the deployment process for you. If you provide a Dockerfile and build context, Defang will upload the files found within the build context to the cloud (either yours in [Defang BYOC](./defang-byoc.md) or ours in [Defang Playground](./defang-playground.md)), build the image, and store it in the cloud provider's container registry. +When you deploy using Defang, whether it's with `defang compose up` with a [Compose file](./compose.md) or using a [Pulumi program](./pulumi.md), Defang will build your services in the cloud and manage the deployment process for you. If you provide a Dockerfile and build context, Defang will upload the files found within the build context to your cloud account via [Defang BYOC](./defang-byoc.md), build the image, and store it in the cloud provider's container registry. ## Deploying Updates @@ -18,7 +18,7 @@ Defang can deploy your services using different [modes](/docs/concepts/deploymen By default, using the `affordable` mode, Defang will deprovision your existing services before provisioning replacements. This helps reduce costs. :::info -In [Defang BYOC](./defang-byoc.md), Defang uses your cloud provider account to build and store your images. In [Defang Playground](./defang-playground.md), we build and store your images for you. +In [Defang BYOC](./defang-byoc.md), Defang uses your cloud provider account to build and store your images. ::: diff --git a/docs/concepts/domains.mdx b/docs/concepts/domains.mdx index 110bbc0d94..508579cc66 100644 --- a/docs/concepts/domains.mdx +++ b/docs/concepts/domains.mdx @@ -17,22 +17,11 @@ To make your service accessible from the public internet with Defang-hosted doma Defang-hosted domains use a structure that is based on your username and service name. - - -If you have a publicly accessible service, you will automatically receive a domain to access it. If you're deploying to the [Defang Playground](./defang-playground.md), your domain will be structured as follows: - -``` -https://---.defang.dev -``` - - -If you're using [Defang BYOC](./defang-byoc.md), your domain will be: +If you have a publicly accessible service, you will automatically receive a domain to access it. When using [Defang BYOC](./defang-byoc.md), your domain will be structured as follows: ``` https://--...defang.app ``` - - ### Sample Configuration @@ -72,9 +61,9 @@ const service = new defang.DefangService("serviceName", { You can also bring your own domain to a Defang project. This allows you to use your own domain name to access your services, and varies a little bit depending on your setup. -### BYOC or Defang Playground +### BYOC without Cloud-hosted DNS -If you are using [Defang BYOC](./defang-byoc.md) and *do not* have your domain's DNS hosted with your cloud provider, or if you are using the [Defang Playground](./defang-playground.md), you will need to follow this flow: +If you are using [Defang BYOC](./defang-byoc.md) and *do not* have your domain's DNS hosted with your cloud provider, you will need to follow this flow: 1. Add the `domainname` to your service definition. 2. Run `defang compose up` to deploy your project. @@ -109,7 +98,7 @@ services: :::warning -As of now, the Pulumi provider does not support [Defang BYOC](./defang-byoc.md) and the [Defang Playground](./defang-playground.md) does not support bringing your own domain, since it is not for production use. +As of now, the Pulumi provider does not support [Defang BYOC](./defang-byoc.md). ::: @@ -118,7 +107,6 @@ As of now, the Pulumi provider does not support [Defang BYOC](./defang-byoc.md) | Provider | BYOD | | --- | --- | -| [Playground](/docs/providers/playground) | ✅ no apex domains | | [AWS](/docs/providers/aws) | ✅ | | [DigitalOcean](/docs/providers/digitalocean) | ❌ | | [GCP](/docs/providers/gcp) | ✅ | diff --git a/docs/concepts/estimation.md b/docs/concepts/estimation.md index f9e60f4b54..1390e683d8 100644 --- a/docs/concepts/estimation.md +++ b/docs/concepts/estimation.md @@ -67,7 +67,6 @@ defang compose up [--provider aws|gcp|digitalocean] [--mode affordable|balanced| | Provider | Estimation Support | |----------------|:------------------:| -| Playground | ❌ | | AWS | ✅ | | DigitalOcean | ❌ | | GCP | ✅ | diff --git a/docs/concepts/managed-llms/managed-language-models.md b/docs/concepts/managed-llms/managed-language-models.md index 7983594a97..63459eab2d 100644 --- a/docs/concepts/managed-llms/managed-language-models.md +++ b/docs/concepts/managed-llms/managed-language-models.md @@ -11,7 +11,6 @@ Each cloud provider offers their own managed Large Language Model services. AWS | Provider | Managed Language Models | | --- | --- | -| [Playground](/docs/providers/playground#managed-llms) | ✅ | | [AWS Bedrock](/docs/providers/aws#managed-llms) | ✅ | | [DigitalOcean GenAI](/docs/providers/digitalocean#future-improvements) | ❌ | | [GCP Vertex AI](/docs/providers/gcp#managed-llms) | ✅ | @@ -45,6 +44,3 @@ Defang has a [*Managed LLM sample*](https://github.com/DefangLabs/samples/tree/m ::: -## Managed LLM on Playground -If you are using the Managed LLM feature on [Defang Playground](/docs/concepts/defang-playground), please note that your `MODEL` (model ID) will be limited to a default model chosen by Defang. -To access a full range of models, consider using [Defang BYOC](/docs/concepts/defang-byoc). diff --git a/docs/concepts/managed-llms/openai-access-gateway.md b/docs/concepts/managed-llms/openai-access-gateway.md index c41b22af34..1795612ffd 100644 --- a/docs/concepts/managed-llms/openai-access-gateway.md +++ b/docs/concepts/managed-llms/openai-access-gateway.md @@ -46,7 +46,6 @@ This can be configured through the following environment variables: | Provider | Managed Language Models | | --- | --- | -| [Playground](/docs/providers/playground#managed-services) | ✅ | | [AWS Bedrock](/docs/providers/aws#managed-llms) | ✅ | | [DigitalOcean GenAI](/docs/providers/digitalocean#future-improvements) | ❌ | | [GCP Vertex AI](/docs/providers/gcp#managed-llms) | ✅ | diff --git a/docs/concepts/managed-storage/managed-mongodb.md b/docs/concepts/managed-storage/managed-mongodb.md index 9c636539b2..b20d24e89b 100644 --- a/docs/concepts/managed-storage/managed-mongodb.md +++ b/docs/concepts/managed-storage/managed-mongodb.md @@ -15,7 +15,6 @@ Managed MongoDB is a service that allows you to store and retrieve large amounts | Provider | Managed MongoDB | | --- | --- | -| [Playground](/docs/providers/playground#managed-services) | ⚠️ Unmanaged | | [AWS](/docs/providers/aws#managed-storage) | ✅ DocumentDB | | [DigitalOcean](/docs/providers/digitalocean#future-improvements) | ⚠️ Unmanaged | | [GCP](/docs/providers/gcp#future-improvements) | ✅ Firestore | diff --git a/docs/concepts/managed-storage/managed-object-storage.md b/docs/concepts/managed-storage/managed-object-storage.md index 88fd2e7cc9..36f78c45a9 100644 --- a/docs/concepts/managed-storage/managed-object-storage.md +++ b/docs/concepts/managed-storage/managed-object-storage.md @@ -15,7 +15,6 @@ Managed Object Storage, like AWS S3, is a service that allows you to store and r | Provider | Managed Object Storage | | --- | --- | -| [Playground](/docs/providers/playground#managed-services) | ❌ | | [AWS](/docs/providers/aws#managed-storage) | ❌ | | [DigitalOcean](/docs/providers/digitalocean#future-improvements) | ❌ | | [GCP](/docs/providers/gcp#future-improvements) | ❌ | diff --git a/docs/concepts/managed-storage/managed-postgres.mdx b/docs/concepts/managed-storage/managed-postgres.mdx index 6ef82b9187..588bcba715 100644 --- a/docs/concepts/managed-storage/managed-postgres.mdx +++ b/docs/concepts/managed-storage/managed-postgres.mdx @@ -11,7 +11,6 @@ Postgres, or PostgreSQL, is a powerful open-source relational database system kn | Provider | Managed Postgres | | --- | --- | -| [Playground](/docs/providers/playground#managed-services) | ⚠️ Unmanaged | | [AWS](/docs/providers/aws#managed-storage) | ✅ RDS Postgres | | [DigitalOcean](/docs/providers/digitalocean#future-improvements) | ⚠️ Unmanaged | | [GCP](/docs/providers/gcp#managed-storage) | ✅ Cloud SQL Postgres | diff --git a/docs/concepts/managed-storage/managed-redis.md b/docs/concepts/managed-storage/managed-redis.md index a5044d64d3..395fc6b4a0 100644 --- a/docs/concepts/managed-storage/managed-redis.md +++ b/docs/concepts/managed-storage/managed-redis.md @@ -11,7 +11,6 @@ Redis is an in-memory data structure store widely used for caching, real-time an | Provider | Managed Redis | | --- | --- | -| [Playground](/docs/providers/playground#managed-services) | ⚠️ Unmanaged | | [AWS](/docs/providers/aws#managed-storage) | ✅ Elasticache | | [DigitalOcean](/docs/providers/digitalocean#future-improvements) | ⚠️ Unmanaged | | [GCP](/docs/providers/gcp#managed-redis) | ✅ Memorystore | diff --git a/docs/concepts/networking.mdx b/docs/concepts/networking.mdx index b774bd0c15..43ed7eee97 100644 --- a/docs/concepts/networking.mdx +++ b/docs/concepts/networking.mdx @@ -2,8 +2,6 @@ title: Networking description: Defang helps you safely configure your services' networking. --- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; # Networking @@ -106,26 +104,11 @@ services: ### Internal DNS -Internal communication is handled slightly differently between the Defang Playground and Defang BYOC. - - - -Internal communication between services in the Defang Playground follows the following pattern: - -``` -http://-: -``` - -The Defang CLI applies the `` prefix when it detects service names in the values of environment variables. - - -Internal communication between services in Defang BYOC follows the following pattern: +Internal communication between services follows this pattern: ``` http://: ``` - - ### Custom Network CIDR diff --git a/docs/concepts/observability.md b/docs/concepts/observability.md index 67c64f2dcd..405e8b7333 100644 --- a/docs/concepts/observability.md +++ b/docs/concepts/observability.md @@ -13,9 +13,6 @@ When you deploy a service using the `defang compose up`, the CLI will automatica Defang has a tutorial on how you can [monitor your services' status and logs](/docs/tutorials/monitoring-your-services). ::: -:::warning -Keep in mind that the [Defang Portal](./portal.md) only displays services deployed to Defang Playground. -::: ## Tail diff --git a/docs/concepts/one-off-jobs.md b/docs/concepts/one-off-jobs.md index fa00947cff..1434b3d3da 100644 --- a/docs/concepts/one-off-jobs.md +++ b/docs/concepts/one-off-jobs.md @@ -137,7 +137,6 @@ One off jobs are deployed as temporary containers on the same infrastructure as | Provider | Release Task Support | |----------------|:--------------------:| -| Playground | ✅ | | AWS | ✅ | | DigitalOcean | ❌ | | GCP | ✅ | diff --git a/docs/concepts/portal.md b/docs/concepts/portal.md index 5150d10734..ba88619bb6 100644 --- a/docs/concepts/portal.md +++ b/docs/concepts/portal.md @@ -5,15 +5,10 @@ description: You can log into the Defang Portal to view the state of your Defang # Portal -You can log into the Defang Portal at [portal.defang.dev](https://portal.defang.dev) using your [Defang account](./accounts.md) to view the state of your Defang services running in the Defang Playground for non-production applications. +You can log into the Defang Portal at [portal.defang.dev](https://portal.defang.dev) using your [Defang account](./accounts.md) to view the state of your Defang services. You can use the Portal to get an overview of your [services](/docs/concepts/services), view the logs for each service, quickly access exposed ports, view environment variables, and more. The Portal is also where you manage your [workspaces](./workspaces.md), invite team members, and configure billing. -:::info -The Defang Portal displays services deployed to Defang Playground. -To view services deployed to Defang BYOC, please check out [Monitoring Your Services](/docs/tutorials/monitoring-your-services). -::: - :::tip Need help with a failing deployment? Defang provides a tool to help [debug](/docs/concepts/debug) in your application. ::: diff --git a/docs/concepts/pulumi.md b/docs/concepts/pulumi.md index 02a96a4428..ac8ed0df18 100644 --- a/docs/concepts/pulumi.md +++ b/docs/concepts/pulumi.md @@ -9,7 +9,7 @@ import TabItem from '@theme/TabItem'; # Pulumi :::warning -Pulumi support is currently only available for Defang Playground. We are working on support for Defang BYOC. +Pulumi support is currently only available for deploying to Defang's infrastructure. We are working on support for Defang BYOC. ::: [Pulumi](https://www.pulumi.com) is a modern infrastructure-as-code toolkit that allows developers to use a programming language like Typescript to provision and manage cloud resources. diff --git a/docs/concepts/railpack.md b/docs/concepts/railpack.md index deb4966518..7e80ef7d99 100644 --- a/docs/concepts/railpack.md +++ b/docs/concepts/railpack.md @@ -148,7 +148,6 @@ services: | Provider | Railpack Support | |----------------|:----------------:| -| Playground | ✅ | | AWS | ✅ | | DigitalOcean | ❌ | | GCP | ✅ | diff --git a/docs/concepts/scaling.md b/docs/concepts/scaling.md index 485b9d0b75..53615b4b4e 100644 --- a/docs/concepts/scaling.md +++ b/docs/concepts/scaling.md @@ -68,7 +68,6 @@ Auto-scaling systems typically rely on: | Provider | Auto-Scaling Support | |----------------|:--------------------:| -| Playground | ❌ | | AWS | ✅ | | DigitalOcean | ❌ | | GCP | ✅ | diff --git a/docs/concepts/services.md b/docs/concepts/services.md index 9c21054fbf..d6c05ca768 100644 --- a/docs/concepts/services.md +++ b/docs/concepts/services.md @@ -3,8 +3,6 @@ title: Services description: Defang allows you to deploy services, defined as containers, to the cloud. --- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; # Services @@ -19,20 +17,11 @@ Defang identifies services by using your [account username](/docs/concepts/accou Service names are defined in your Compose file or in your Pulumi program. ::: - - - Domains for services in Playground follow the following pattern: - ``` - ---.prod1a.defang.dev - ``` - - - Domains for services in Defang BYOC follow the following pattern: - ``` - --...defang.app - ``` - - +Domains for services follow this pattern: + +``` +--...defang.app +``` ### Service Deployment diff --git a/docs/intro/faq/questions.md b/docs/intro/faq/questions.md index 0eeb87942f..4a43b4f98b 100644 --- a/docs/intro/faq/questions.md +++ b/docs/intro/faq/questions.md @@ -11,7 +11,7 @@ import {Button, ButtonGroup, FormGroup, FormLabel} from "@mui/material" ### Which cloud/region is the app being deployed to? -- In the [Defang Playground](/docs/concepts/defang-playground), the app is deployed to AWS `us-west-2`. In the [Defang BYOC](/docs/concepts/defang-byoc) model, the region is determined by your Defang BYOC [Provider](/docs/providers) settings. +- The region is determined by your [Defang BYOC](/docs/concepts/defang-byoc) [Provider](/docs/providers) settings. ### Can I bring my own AWS or other cloud account? @@ -66,10 +66,10 @@ import {Button, ButtonGroup, FormGroup, FormLabel} from "@mui/material" ## Feature Comparisons ### Is Defang a run-time platform? -- No. Defang is not a run-time platform. Instead, it lets you host and run your application on a [cloud provider](/docs/providers) of your choice. You can think of it as a tool that makes it way easier to deploy to that cloud provider. We do provide [Defang Playground](/docs/concepts/defang-playground), but it is meant to be used as a testing environment only. +- No. Defang is not a run-time platform. Instead, it lets you host and run your application on a [cloud provider](/docs/providers) of your choice. You can think of it as a tool that makes it way easier to deploy to that cloud provider. ### What is the difference between Defang and platforms such as Vercel, fly.io, Railway, Render, or Heroku? -- Defang is a tool that helps you get your application deployed to a [cloud provider](/docs/providers) of your choice, and it is not a platform. Unlike platforms, Defang does not host your application. We do provide [Defang Playground](/docs/concepts/defang-playground), but it is meant to be used as a testing environment only. +- Defang is a tool that helps you get your application deployed to a [cloud provider](/docs/providers) of your choice, and it is not a platform. Unlike platforms, Defang does not host your application. ### What is the difference between Defang and tools such as SST? - Defang is cloud-agnostic and language-agnostic, meaning that it is designed to work with different [cloud providers](/docs/providers), and programming languages. Since Defang is not tied to just one cloud or language, this allows for greater flexibility in a wide range of cases. Another difference is that Defang follows the [Compose specification](https://docs.docker.com/compose/compose-file/), allowing it to work smoothly with various container platforms such as Docker. diff --git a/docs/intro/getting-started.mdx b/docs/intro/getting-started.mdx index f0d85b1e99..cf1d14114d 100644 --- a/docs/intro/getting-started.mdx +++ b/docs/intro/getting-started.mdx @@ -106,7 +106,7 @@ You can open the folder in your favorite editor and see the files that were gene * The `Dockerfile` is used to build the container image for your service. * The `compose.yaml` file is used to define the services you want to deploy. -## Deploy to the Playground +## Deploy Go back to your shell and type the following: @@ -138,7 +138,7 @@ When you do this, you should see something similar to the output below: 2024-09-19T10:51:05.536299-07:00 cd Update succeeded in 11.99769745s ; provisioning... 2024-09-19T10:51:39.419693-07:00 app Server running at http://0.0.0.0:3000/ * Service app is in state DEPLOYMENT_COMPLETED and will be available at: - - https://jordanstephens-app--3000.prod1.defang.dev + - https://app--3000.prod1.jordanstephens.defang.app * Done. ``` diff --git a/docs/intro/intro.mdx b/docs/intro/intro.mdx index a25af42aad..15194bf6f5 100644 --- a/docs/intro/intro.mdx +++ b/docs/intro/intro.mdx @@ -30,17 +30,11 @@ import DocCardList from "@docusaurus/theme-classic/lib/theme/DocCardList"; label: "CLI Reference", description: "Use the Defang CLI to deploy your app", }, - { - type: "link", - href: "/docs/tutorials/deploy-to-playground", - label: "Try Defang", - description: "Deploy to our free Playground", - }, { type: "link", href: "/docs/tutorials/deploy-to-your-cloud", - label: "Deploy to your own cloud", - description: "When you're ready for production", + label: "Deploy to your cloud", + description: "Deploy to your own cloud account", }, ]} /> diff --git a/docs/intro/what-is-defang.mdx b/docs/intro/what-is-defang.mdx index ec0be9ad85..29d0c2f00a 100644 --- a/docs/intro/what-is-defang.mdx +++ b/docs/intro/what-is-defang.mdx @@ -22,8 +22,7 @@ The [Defang CLI (command line interface)](/docs/intro/getting-started#install-th Defang can automatically build and deploy your project with a single command. - - If you’re new to Defang, you can try deploying to [Defang Playground](/docs/concepts/defang-playground.md), a hosted environment to learn to use Defang with non-production workloads. - - Once you’re ready, you can [deploy](/docs/tutorials/deploy-to-your-cloud) a project to your own cloud account - we call this [Defang BYOC (Bring-your-Own-Cloud)](/docs/concepts/defang-byoc.md). We offer support for the following cloud providers: + - You can [deploy](/docs/tutorials/deploy-to-your-cloud) a project to your own cloud account - we call this [Defang BYOC (Bring-your-Own-Cloud)](/docs/concepts/defang-byoc.md). We offer support for the following cloud providers: * [Amazon Web Services (AWS)](/docs/tutorials/deploy-to-aws) * [DigitalOcean](/docs/tutorials/deploy-to-digitalocean) * [Google Cloud Platform (GCP)](/docs/tutorials/deploy-to-gcp) diff --git a/docs/providers/playground.md b/docs/providers/playground.md deleted file mode 100644 index ae70a9e1dc..0000000000 --- a/docs/providers/playground.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: Playground -description: The Defang Playground is a free tier that allows you to experiment with Defang. -sidebar_position: 10 ---- - -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/intro/getting-started). - -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. - -:::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). - -### 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. diff --git a/docs/tutorials/adding-custom-one-click-deploy.md b/docs/tutorials/adding-custom-one-click-deploy.md index 30bd9f96d1..6566f2463d 100644 --- a/docs/tutorials/adding-custom-one-click-deploy.md +++ b/docs/tutorials/adding-custom-one-click-deploy.md @@ -9,7 +9,7 @@ import { URLProvider, URLEncode } from "../../src/components/OneClick"; # Adding Custom 1-Click Deploy to Your App -This tutorial will show you how to add a 1-Click Deploy link so other people can easily deploy your app to the Defang Playground and eventually to their own cloud accounts. +This tutorial will show you how to add a 1-Click Deploy link so other people can easily deploy your app to their own cloud accounts using Defang. The link is often placed as a button in the `README.md` file of your project repository, and is the easiest way to allow anyone to deploy your app. @@ -47,7 +47,7 @@ on: jobs: deploy: - environment: playground + environment: production runs-on: ubuntu-latest permissions: contents: read diff --git a/docs/tutorials/deploy-to-playground.mdx b/docs/tutorials/deploy-to-playground.mdx deleted file mode 100644 index 8a38b2f36d..0000000000 --- a/docs/tutorials/deploy-to-playground.mdx +++ /dev/null @@ -1,69 +0,0 @@ ---- -title: Deploy to Playground -description: Deploy to the free Defang Playground. ---- - -# Deploy to Playground - -This tutorial will show you how to deploy your project to the free [Defang Playground](/docs/concepts/defang-playground). - -## Prerequisites - -- [The Defang CLI](/docs/intro/getting-started#install-the-defang-cli) -- [A Defang Account](/docs/concepts/authentication) -- [A `compose.yaml` file in your project](https://docs.docker.com/compose/gettingstarted/) -- [A Dockerfile in your project](https://docs.docker.com/get-started/docker-concepts/building-images/writing-a-dockerfile/) or use [Railpack](../concepts/railpack.md) - -## CLI - -### Step 1 - Navigate to your project directory - -Head to the folder where your project is located. - -```bash -$ cd path/to/your/project -``` - -### Step 2 - Deploy - -``` -$ defang compose up -``` - -If you have not used Defang before, you'll be prompted to log in. - -``` - ! Please log in to continue. -Please visit http://127.0.0.1:49154 and log in. (Right click the URL or press ENTER to open browser) -``` - -:::info -To learn more about how authentication works in defang, check out the [authenticating page](/docs/concepts/authentication). -::: - -When you do this, you should see something similar to the output below: - -``` - * Uploading build context for app - * Deploying service app - * Monitor your services' status in the defang portal - - https://portal.defang.dev/service/app - * Tailing logs for deployment ID o59k89vk3qc8 ; press Ctrl+C to detach: - * Press V to toggle verbose mode -2024-09-19T10:50:53.572443-07:00 cd Update started for stack jordanstephens-prod1 -2024-09-19T10:51:05.536299-07:00 cd Update succeeded in 11.99769745s ; provisioning... -2024-09-19T10:51:39.419693-07:00 app Server running at http://0.0.0.0:3000/ - * Service app is in state DEPLOYMENT_COMPLETED and will be available at: - - https://jordanstephens-app--3000.prod1.defang.dev - * Done. -``` - -You can also check on your deployment on the on the [Defang portal](#defang-portal) as well. - ---- - -## Defang Portal - -Now we can go to [https://portal.defang.dev/service/app](https://portal.defang.dev/service/app) to see our service listed in the Defang portal. - -![screenshot of the defang portal](/img/getting-started-portal.png) diff --git a/docs/tutorials/deploy-to-your-cloud.mdx b/docs/tutorials/deploy-to-your-cloud.mdx index 509ed8e449..b82c5f38ae 100644 --- a/docs/tutorials/deploy-to-your-cloud.mdx +++ b/docs/tutorials/deploy-to-your-cloud.mdx @@ -9,7 +9,6 @@ This tutorial will show you how to deploy your services to your own cloud accoun :::tip Defang makes it easier to deploy to any cloud—in your *own* cloud accounts. We refer to this as [bring-your-own-cloud (BYOC)](/docs/concepts/defang-byoc). -If you aren't ready to deploy to your own cloud account, you can use the [Defang Playground](/docs/concepts/defang-playground) to get a feel for how Defang works for free. ::: ## Choose your cloud diff --git a/docs/tutorials/deploy-using-pulumi.mdx b/docs/tutorials/deploy-using-pulumi.mdx index 7d66046453..238b127c8d 100644 --- a/docs/tutorials/deploy-using-pulumi.mdx +++ b/docs/tutorials/deploy-using-pulumi.mdx @@ -5,7 +5,7 @@ title: Deploy Using Pulumi # Deploy Using Pulumi :::warning -At the time of writing, the Defang Pulumi Provider only works with [Defang Playground](../concepts/defang-playground.md). We are working on [BYOC](../concepts/defang-byoc.md) support. +At the time of writing, the Defang Pulumi Provider does not yet support [BYOC](../concepts/defang-byoc.md). We are working on adding support. ::: This tutorial will show you how to deploy Minio with Pulumi using the Defang Provider. @@ -124,7 +124,7 @@ defang tail --name minio ### Logging Into Minio -The [Defang Playground](../concepts/defang-playground.md) will give you a domain, which you can obtain by running the following command: +Defang will give you a domain, which you can obtain by running the following command: ```bash defang ls | grep 'minio.*9001' diff --git a/docs/tutorials/deploy-with-gpu.mdx b/docs/tutorials/deploy-with-gpu.mdx index e517565398..5c77352507 100644 --- a/docs/tutorials/deploy-with-gpu.mdx +++ b/docs/tutorials/deploy-with-gpu.mdx @@ -9,7 +9,7 @@ This tutorial will show you how to create and deploy a GPU-powered application o We will walk you through the whole deployment process based on the [Mistral & vLLM](https://github.com/DefangLabs/samples/tree/main/samples/vllm) sample. :::info -Note that GPU deployments are not permitted on the Defang Playground. You must [upgrade to a paid account](https://defang.io/pricing/) and [deploy to your own cloud account](/docs/tutorials/deploy-to-your-cloud). +GPU deployments require a paid account. You must [upgrade to a paid account](https://defang.io/pricing/) and [deploy to your own cloud account](/docs/tutorials/deploy-to-your-cloud). :::