prefer "defang compose up" to "defang up"

jordanstephens · jordanstephens · commit c0dac0011847 · 2024-12-04T08:32:22.000-05:00
diff --git a/docs/concepts/defang-byoc.md b/docs/concepts/defang-byoc.md
@@ -22,7 +22,7 @@ The Defang CLI can be configured to deploy to a cloud provider either by using t
 ```bash
 # Supported provider values: auto, aws, defang, digitalocean
 # Default is auto, which deploys to the Defang Playground but warns if it detects cloud credentials
-$ defang up --provider=aws
+$ defang compose up --provider=aws
 # or
 $ export DEFANG_PROVIDER=digitalocean
 ```
@@ -43,9 +43,9 @@ 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! 
+Google Cloud Platform (GCP) support is coming soon to Defang. Stay tuned for updates!
 :::
-Please check out the [GCP Provider](../providers/gcp/) page for more details. 
+Please check out the [GCP Provider](../providers/gcp/) page for more details.
 
 ## Azure
 
diff --git a/docs/faq/questions.md b/docs/faq/questions.md
@@ -33,15 +33,15 @@ import {Button, ButtonGroup, FormGroup, FormLabel} from "@mui/material"
 
 ### Can I run production apps with Defang?
 
-- Yes! Defang makes it easy to deploy your app on production-ready infrastructure in your own cloud account. For example, you can deploy your app to AWS with `defang up --provider=aws --mode=production`. Check out your preferred cloud provider on [Defang BYOC](../concepts/defang-byoc.md).
+- Yes! Defang makes it easy to deploy your app on production-ready infrastructure in your own cloud account. For example, you can deploy your app to AWS with `defang compose up --provider=aws --mode=production`. Check out your preferred cloud provider on [Defang BYOC](../concepts/defang-byoc.md).
 
 ### Does Defang support blue/green deployments?
 
-- Defang does not currently support Blue/Green deploys, but it does support rolling updates with the `production` deployment mode. `defang up --mode=production`.
+- Defang does not currently support Blue/Green deploys, but it does support rolling updates with the `production` deployment mode. `defang compose up --mode=production`.
 
 ### Does Defang support rolling deployments?
 
-- Yes! Defang supports rolling updates with the `production` deployment mode. `defang up --mode=production`.
+- Yes! Defang supports rolling updates with the `production` deployment mode. `defang compose up --mode=production`.
 
 ### Can I cancel a deployment once it has started?
 
@@ -65,7 +65,7 @@ import {Button, ButtonGroup, FormGroup, FormLabel} from "@mui/material"
 - No. Defang is not a run-time platform. Instead, it lets you host and run your application on a [cloud provider](../category/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, and Railway?
-- Defang is a tool that helps you get your application deployed to a [cloud provider](../category/providers) of your choice, and it is not a platform. Unlike platforms, Defang does not host your application. We do provide [Defang Playground](../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](../category/providers) of your choice, and it is not a platform. Unlike platforms, Defang does not host your application. We do provide [Defang Playground](../concepts/defang-playground), but it is meant to be used as a testing environment only.
 
 ### 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](../category/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.
@@ -83,4 +83,3 @@ import {Button, ButtonGroup, FormGroup, FormLabel} from "@mui/material"
 ### I'm getting a warning/error. What does it mean?
 
 - Please see the [Common Error Messages](./warnings-errors.md) page.
-
diff --git a/docs/getting-started.mdx b/docs/getting-started.mdx
@@ -111,7 +111,7 @@ You can open the folder in your favorite editor and see the files that were gene
 Go back to your shell and type the following:
 
 ```
-$ defang up
+$ defang compose up
 ```
 
 If you have not used Defang before, you'll be prompted to log in.
diff --git a/docs/providers/aws/aws.md b/docs/providers/aws/aws.md
@@ -19,7 +19,7 @@ If you have the AWS CLI installed, you should be able to successfully run `aws s
 Use the `--provider=aws` flag to tell the Defang CLI to use the AWS Provider or set the `DEFANG_PROVIDER` environment variable to `aws`.
 
 ```bash
-$ defang up --provider=aws
+$ defang compose up --provider=aws
 # or
 $ export DEFANG_PROVIDER=aws
 ```
diff --git a/docs/providers/digitalocean/digitalocean.md b/docs/providers/digitalocean/digitalocean.md
@@ -42,7 +42,7 @@ The Defang CLI will automatically check if these envinonment variables are set b
 Once you are ready to go, add the `--provider=digitalocean` to your command to tell the Defang CLI to use the DigitalOcean provider.
 
 ```bash
-$ defang up --provider=digitalocean
+$ defang compose up --provider=digitalocean
 # or
 $ export DEFANG_PROVIDER=digitalocean
 ```
diff --git a/docs/tutorials/deploy-to-aws.mdx b/docs/tutorials/deploy-to-aws.mdx
@@ -4,7 +4,7 @@ description: Defang allows you deploy to your own Amazon Web Services (AWS) acco
 sidebar_position: 11
 ---
 
-# Deploy to Amazon Web Services (AWS) 
+# Deploy to Amazon Web Services (AWS)
 
 This tutorial will show you how to deploy your services to your own AWS account using Defang.
 
@@ -34,12 +34,12 @@ If you have the AWS CLI installed (which is not required in order to use the Def
 
 ## Step 3 - Deploy
 
-Invoke the `defang up` CLI command with the `--provider=aws` flag or set the `DEFANG_PROVIDER=aws` environment variable.
+Invoke the `defang compose up` CLI command with the `--provider=aws` flag or set the `DEFANG_PROVIDER=aws` environment variable.
 
 For example:
 
 ```bash
-$ defang up --provider=aws
+$ defang compose up --provider=aws
 ```
 
 ## Step 4 - Inspect your deployment
diff --git a/docs/tutorials/deploy-to-digitalocean.mdx b/docs/tutorials/deploy-to-digitalocean.mdx
@@ -31,12 +31,12 @@ Defang will look for your DigitalOcean credentials in your shell environment and
 
 ## Step 3 - Deploy
 
-Invoke the `defang up` CLI command with the `--provider=do` flag or set the `DEFANG_PROVIDER=do` environment variable.
+Invoke the `defang compose up` CLI command with the `--provider=do` flag or set the `DEFANG_PROVIDER=do` environment variable.
 
 For example:
 
 ```bash
-$ defang up --provider=do
+$ defang compose up --provider=do
 ```
 
 ## Step 4 - Inspect your deployment
diff --git a/docs/tutorials/deploy-to-playground.mdx b/docs/tutorials/deploy-to-playground.mdx
@@ -23,7 +23,7 @@ $ cd path/to/your/project
 ## Step 2 - Deploy
 
 ```
-$ defang up
+$ defang compose up
 ```
 
 If you have not used Defang before, you'll be prompted to log in.
