From 1b6e71ea1b3911ec7371ec2d0f8cfc5b4ddb1bcb Mon Sep 17 00:00:00 2001 From: commit111 Date: Mon, 16 Dec 2024 16:29:27 -0800 Subject: [PATCH] minor fixes/rewordings --- docs/concepts/defang-byoc.md | 4 ++-- docs/faq/warnings-errors.md | 6 +++--- docs/providers/azure.md | 2 +- docs/providers/digitalocean/digitalocean.md | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/concepts/defang-byoc.md b/docs/concepts/defang-byoc.md index 537a1854f..e351c6f10 100644 --- a/docs/concepts/defang-byoc.md +++ b/docs/concepts/defang-byoc.md @@ -35,7 +35,7 @@ Please read the [AWS Provider](../providers/aws/aws.md) documentation for more d :::info -The Public Preview of the v1 Defang BYOC DigitalOcean Provider as of October 1 2024. +The Defang DigitalOcean Provider is available for Public Preview as of October 2024. ::: Please read the [DigitalOcean Provider](../providers/digitalocean/digitalocean.md) documentation for more details about how the DigitalOcean provider works and how to get started. @@ -43,7 +43,7 @@ Please read the [DigitalOcean Provider](../providers/digitalocean/digitalocean.m ## GCP :::info -Google Cloud Platform (GCP) support is coming soon to Defang. Stay tuned for updates! +The Defang GCP Provider is available for Public Preview as of December 2024. ::: Please check out the [GCP Provider](../providers/gcp/) page for more details. diff --git a/docs/faq/warnings-errors.md b/docs/faq/warnings-errors.md index caabd0d8e..30a228029 100644 --- a/docs/faq/warnings-errors.md +++ b/docs/faq/warnings-errors.md @@ -90,7 +90,7 @@ services: ### "Stack:… is in UPDATE_COMPLETE_CLEANUP_IN_PROGRESS state and cannot be updated" - This happens if different version of the Defang CLI are used with the same AWS account. Each version one will try to update the CD stack to its version, back and forth. Make sure that all users have the same version of the CLI. Check the CLI version using `defang version`. -### "invalid healthcheck: ingress ports require an HTTP healthcheck on `localhost`. +### "invalid healthcheck: ingress ports require an HTTP healthcheck on `localhost`." - This message is displayed when `defang compose up` tries to deploy a service with an "ingress" port, if the service does not have a `healthcheck` which mentions `localhost`. Defang routes a load balancer to your service's ingress ports, and the loadbalancer needs to be able to check the health of the service. To solve this issue, ask yourself these two questions: @@ -104,7 +104,7 @@ services: - - "1234:1234" + - "1234" ``` -2. Does my healthcheck include the string `localhost`? It is very common to define a healthcheck by using `curl` or `wget` to make a request to `localhost`. So common, in fact, that defang will look for the string `localhost` in your healthcheck definition. For example, this healthcheck is valid: +2. Does my healthcheck include the string `localhost`? It is very common to define a healthcheck by using `curl` or `wget` to make a request to `localhost`. So common, in fact, that Defang will look for the string `localhost` in your healthcheck definition. For example, this healthcheck is valid: ```yaml healthcheck: @@ -118,7 +118,7 @@ services: test: ["CMD", "./my-healthcheck"] ``` -### The build aborted with OutOfMemoryError: Container killed due to memory usage +### "The build aborted with OutOfMemoryError: Container killed due to memory usage" The image build might fail if the build process uses too much memory. The first thing to try is to limit the size of your project by excluding unnecessary files: the easiest way is to create a `.dockerignore` file that excludes irrelevatn files. Note that Defang will use a default `.dockerignore` file if you don't have one, but that default might not work for some projects and it's always better to make a `.dockerignore` file specific to your project. diff --git a/docs/providers/azure.md b/docs/providers/azure.md index 8eaddd948..de7d49c00 100644 --- a/docs/providers/azure.md +++ b/docs/providers/azure.md @@ -7,7 +7,7 @@ sidebar_position: 4000 # Azure :::info -We will be working on Microsoft Azure support in the future. If you are interested in Azure support, please vote on [this issue](https://github.com/DefangLabs/defang/issues/57). +We will be working on Azure support in the future. If you are interested in Azure support, please vote on [this issue](https://github.com/DefangLabs/defang/issues/57). ::: You can learn more about other cloud [providers](/docs/category/providers/). \ No newline at end of file diff --git a/docs/providers/digitalocean/digitalocean.md b/docs/providers/digitalocean/digitalocean.md index dd0cfffd4..748b3c435 100644 --- a/docs/providers/digitalocean/digitalocean.md +++ b/docs/providers/digitalocean/digitalocean.md @@ -10,7 +10,7 @@ sidebar_position: 010 The Defang DigitalOcean Provider is available for Public Preview as of October 2024. ::: -Why should you use Defang with DigitalOcean? Defang allows you to easily create and manage full, scalable applications with DigitalOcean. Defang aims to make it easier to deploy your services to the cloud. DigitalOcean is one of the most popular cloud providers in the world and with Defang, you don't have to waste your time understanding the complexities and challenges of the DigitalOcean platform. Let Defang do it for you and spend more time working on what's important to you! +Why should you use Defang with DigitalOcean? Defang allows you to easily create and manage full, scalable applications with DigitalOcean. Defang aims to make it easier to deploy your services to the cloud. DigitalOcean is one of the most popular cloud providers in the world and with Defang, you can bypass the complexities of the DigitalOcean platform. Let Defang do it for you and spend more time working on what's important to you! ## Getting Started