Skip to content

Commit 1b6e71e

Browse files
committed
minor fixes/rewordings
1 parent 1884950 commit 1b6e71e

File tree

4 files changed

+7
-7
lines changed

4 files changed

+7
-7
lines changed

docs/concepts/defang-byoc.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,15 +35,15 @@ Please read the [AWS Provider](../providers/aws/aws.md) documentation for more d
3535

3636
:::info
3737

38-
The Public Preview of the v1 Defang BYOC DigitalOcean Provider as of October 1 2024.
38+
The Defang DigitalOcean Provider is available for Public Preview as of October 2024.
3939
:::
4040

4141
Please read the [DigitalOcean Provider](../providers/digitalocean/digitalocean.md) documentation for more details about how the DigitalOcean provider works and how to get started.
4242

4343
## GCP
4444

4545
:::info
46-
Google Cloud Platform (GCP) support is coming soon to Defang. Stay tuned for updates!
46+
The Defang GCP Provider is available for Public Preview as of December 2024.
4747
:::
4848
Please check out the [GCP Provider](../providers/gcp/) page for more details.
4949

docs/faq/warnings-errors.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ services:
9090
### "Stack:… is in UPDATE_COMPLETE_CLEANUP_IN_PROGRESS state and cannot be updated"
9191
- 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`.
9292

93-
### "invalid healthcheck: ingress ports require an HTTP healthcheck on `localhost`.
93+
### "invalid healthcheck: ingress ports require an HTTP healthcheck on `localhost`."
9494

9595
- 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:
9696

@@ -104,7 +104,7 @@ services:
104104
- - "1234:1234"
105105
+ - "1234"
106106
```
107-
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:
107+
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:
108108

109109
```yaml
110110
healthcheck:
@@ -118,7 +118,7 @@ services:
118118
test: ["CMD", "./my-healthcheck"]
119119
```
120120

121-
### The build aborted with OutOfMemoryError: Container killed due to memory usage
121+
### "The build aborted with OutOfMemoryError: Container killed due to memory usage"
122122

123123
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.
124124

docs/providers/azure.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ sidebar_position: 4000
77
# Azure
88

99
:::info
10-
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).
10+
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).
1111
:::
1212

1313
You can learn more about other cloud [providers](/docs/category/providers/).

docs/providers/digitalocean/digitalocean.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ sidebar_position: 010
1010
The Defang DigitalOcean Provider is available for Public Preview as of October 2024.
1111
:::
1212

13-
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!
13+
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!
1414

1515
## Getting Started
1616

0 commit comments

Comments
 (0)