Update static-web-apps-cli.md

Author: xmdanni

articles/static-web-apps/static-web-apps-cli.md

@@ -1,4 +1,5 @@
 ---
+description: Azure Static Web Apps CLI reference
 title: Azure Static Web Apps CLI reference
 ms.topic: reference
 ms.date: 07/25/2025
@@ -114,6 +115,16 @@ The following is an example configuration generated by the `init` command:
 ```json
 {
   "$schema": "https://aka.ms/azure/static-web-apps-cli/schema",
+  "configurations": {
+    "myApp": {
+      "appLocation": ".",
+      "apiLocation": "api",
+      "outputLocation": "dist",
+      "appBuildCommand": "npm run build",
+      "apiBuildCommand": "npm run build --if-present",
+      "run": "npm run dev",
+      "appDevserverUrl": "http://localhost:8080"
+    }
   }
 }
 ```
@@ -164,6 +175,10 @@ Common use cases include: installing dependencies for the front-end app and API
 ```azstatic-cli
 swa build
           [--app-location]
+          [--api-location]
+          [--output-location]
+          [--app-build-command]
+          [--api-build-command]
           [--auto]
 ```
 
@@ -229,8 +244,16 @@ Start the Azure Static Web Apps emulator from a directory or bind to a running d
 
 By default, the CLI starts and serves any static content from the current working directory `./`:
 
+```azstatic-cli
+swa start
+```
+
 If the artifact folder of your static app is under a different folder (for example, `./my-dist`), then run the CLI and provide that folder:
 
+```azstatic-cli
+swa start ./my-dist
+```
+
 ### Serve from a dev server
 
 When developing your front-end app locally, it's often useful to use the dev server that comes with your front end framework's CLI. Using the framework CLI allows you to use built-in features like "livereload" and HMR (hot module replacement).
@@ -241,12 +264,39 @@ To use SWA CLI with your local dev server, follow these two steps:
 
 1. In a separate terminal, run `swa start` with the URI provided by the dev server, in the following format:
 
+```azstatic-cli
+swa start http://<APP_DEV_SERVER_HOST>:<APP_DEV_SERVER_PORT>
+```
+
 Here is a list of the default ports and commands used by some popular dev servers:
 
+| Tool | Port | Command |
+|--|--|--|
+| [Angular](https://angular.io/cli) | `4200` | `swa start http://localhost:4200` |
+| [Blazor WebAssembly](https://dotnet.microsoft.com/apps/aspnet/web-apps/blazor) | `5000` | `swa start http://localhost:5000` |
+| [Gatsby](https://www.gatsbyjs.com/docs/reference/gatsby-cli/) | `8000` | `swa start http://localhost:8000` |
+| [Hugo](https://gohugo.io/commands/hugo_server/) | `1313` | `swa start http://localhost:1313` |
+| [Next.js](https://nextjs.org/) | `3000` | `swa start http://localhost:3000` |
+| [React (Create React App)](https://reactjs.org/docs/create-a-new-react-app.html) | `3000` | `swa start http://localhost:3000` |
+| [Svelte (sirv-cli)](https://github.com/lukeed/sirv/tree/master/packages/sirv-cli/) | `5000` | `swa start http://localhost:5000` |
 | [Vue](https://github.com/vuejs/create-vue) | `3000` | `swa start http://localhost:3000` |
 
 Instead of starting a dev server separately, you can provide the startup command to the CLI.
 
+```azstatic-cli
+# npm start script (React)
+swa start http://localhost:3000 --run "npm start"
+
+# dotnet watch (Blazor)
+swa start http://localhost:5000 --run "dotnet watch run"
+
+# Jekyll
+swa start http://localhost:4000 --run "jekyll serve"
+
+# custom script
+swa start http://localhost:4200 --run "./startup.sh"
+```
+
 Then access the application with the emulated services from `http://localhost:4280`
 
 ### Serve both the front-end app and API
@@ -257,6 +307,14 @@ If your project includes API functions, the CLI will check if the Azure Function
 
 Run the CLI and provide the folder that contains the API backend (a valid Azure Functions App project):
 
+```azstatic-cli
+# static content plus an API
+swa start ./my-dist --api-location ./api
+
+# front-end dev server plus an API
+swa start http://localhost:3000 --api-location ./api
+```
+
 #### Start API server manually
 
 When developing your backend locally, sometimes it's useful to run Azure Functions Core Tools separately to serve your API. This allows you to use built-in features like debugging and rich editor support.
@@ -267,9 +325,17 @@ To use the CLI with your local API backend dev server, follow these two steps:
 
 2. In a separate terminal, run the SWA CLI with the `--api-location` flag and the URI of the local API server, in the following format:
 
+```azstatic-cli
+swa start ./my-dist --api-location http://localhost:7071
+```
+
 #### Database connections
 
-To start your application with a [database connection](database-overview.md), use the `--data-api-location` parameter and point to the folder containing the *staticwebapp.database.config.json* file.
+To start your application with a [database connection](database-overview.md), use the `--data-api-location` parameter and point to the folder containing the _staticwebapp.database.config.json_ file.
+
+```azstatic-cli
+swa start ./src --data-api-location swa-db-connections
+```
 
 ### Syntax
 
@@ -389,8 +455,18 @@ The SWA CLI supports deploying using a deployment token. This is often useful wh
 
 - If you are using the [Azure CLI](https://aka.ms/azcli), you can get the deployment token of your project using the following command:
 
+```azstatic-cli
+az staticwebapp secrets list --name <APPLICATION_NAME> --query "properties.apiKey"
+```
+
 - If you are using the Azure Static Web Apps CLI, you can use the following command:
 
+```azstatic-cli
+swa deploy --print-token
+```
+
+You can then use that value with the `--deployment-token <TOKEN>` or you can create an environment variable called `SWA_CLI_DEPLOYMENT_TOKEN` and set it to the deployment token.
+
   > **Important**: Don't store the deployment token in a public repository. This value must remain a secret.
 
 ### Deploy a front end app without an API
@@ -401,6 +477,11 @@ You can deploy a front end application without an API to Azure Static Web Apps b
 
 **Option 1:** From build folder you would like to deploy, run the deploy command:
 
+```azstatic-cli
+cd build/
+swa deploy
+```
+
   > **Note**: The `build` folder must contain the static content of your app that you want to deploy.
 
 **Option 2:** You can also deploy a specific folder:
@@ -409,14 +490,102 @@ You can deploy a front end application without an API to Azure Static Web Apps b
 
 2. Deploy your app:
 
+```azstatic-cli
+swa deploy ./my-dist
+```
+
 ### Deploy a front-end app with an API
 
 To deploy both the front end app and an API to Azure Static Web Apps, use the following steps:
 
+1. If your front end application requires a build step, run `swa build` or refer to your application build instructions.
+
+2. Make sure the API language runtime version in the `staticwebapp.config.json` file is set correctly, for example:
+
+```json
+{
+  "platform": {
+    "apiRuntime": "node:16"
+  }
+}
+```
+
+  > **Note**: If your project doesn't have any `staticwebapp.config.json` file, add one under your `outputLocation` folder.
+
+3. Deploy your app:
+
+```azstatic-cli
+swa deploy ./my-dist --api-location ./api
+```
+
+### Deploy a Blazor app
+
+To deploy a Blazor app with an optional API to Azure Static Web Apps, use the following steps:
+
+1. Build your Blazor app in **Release** mode:
+
+```azstatic-cli
+dotnet publish -c Release -o bin/publish
+```
+
+2. From the root of your project, run the `deploy` command:
+
+```azstatic-cli
+swa deploy ./bin/publish/wwwroot --api-location ./Api
+```
+
+### Deploy using the `swa-cli.config.json`
+
+> **Note**: The path for `outputLocation` must be relative to the `appLocation`.
+
+If you are using a `swa-cli.config.json` configuration file in your project and have a single configuration entry, use a configuration like this:
+
+```json
+{
+  "configurations": {
+    "my-app": {
+      "appLocation": "./",
+      "apiLocation": "api",
+      "outputLocation": "frontend",
+      "start": {
+        "outputLocation": "frontend"
+      },
+      "deploy": {
+        "outputLocation": "frontend"
+      }
+    }
+  }
+}
+```
+
+Then you can deploy your application by running the following steps:
+
+1. If your front-end application requires a build step, run `swa build` or refer to your application build instructions.
+
+2. Deploy your app:
+
+```azstatic-cli
+swa deploy
+```
+
+If you have multiple configuration entries, you can provide the entry ID to specify which one to use:
+
+```azstatic-cli
+swa deploy my-otherapp
+```
+
 ### Syntax
 
 ```azstatic-cli
 swa deploy
+           [--api-location]
+           [--app-location]
+           [--output-location]
+           [--deployment-token]
+           [--env]
+           [--print-token]
+           [--data-api-location]
+           [--swa-config-location]
 ```
 
 ### Examples
@@ -453,6 +622,38 @@ swa deploy --env production
 
 ### Parameters
 
+___`--app-location, -a <PATH>`___
+
+The folder containing the source code of the front-end application. Default is `.`.
+
+___`--api-location, -i <PATH>`___
+
+The folder containing the source code of the API application.
+
+___`--output-location, -O <PATH>`___
+
+The folder containing the built source of the front-end application. The path is relative to `--app-location`. Default is `.`.
+
+___`--deployment-token, -t <TOKEN>`___
+
+Secret token used to authenticate with the Azure Static Web Apps service.
+
+___`--env, -e <ENVIRONMENT_NAME>`___
+
+Named environment that you want to deploy to.
+
+___`--print-token`___
+
+Print the deployment token for the Static Web Apps resource.
+
+___`--data-api-location, -d <PATH>`___
+
+The folder containing the database configuration file.
+
+___`--swa-config-location, -w <PATH>`___
+
+The path to the directory containing the staticwebapp.config.json file used for the deployment.
+
 ___[Global Parameters](#global-parameters)___
 
 ## swa db