You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/frontend/src/content/docs/deployment/index.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ import CTABanner from '@components/CTABanner.astro';
22
22
icon="rocket"
23
23
title="From dev to production,"
24
24
highlight="seamlessly."
25
-
subtitle="Use aspire publish to emit deployment artifacts as a one-way handoff for external or manual use, or use aspire deploy to let Aspire generate, resolve, and apply changes directly."
25
+
subtitle="Use `aspire publish` to emit deployment artifacts as a one-way handoff for external or manual use, or use `aspire deploy` to let Aspire generate, resolve, and apply changes directly."
@@ -65,7 +65,7 @@ A pipeline step is a named unit of work in the Aspire pipeline. Any resource can
65
65
|[`aspire deploy`](/reference/cli/commands/aspire-deploy/)| The deploy entry point | Generate target-specific output, resolve parameters, and apply deployment changes directly |
66
66
|[`aspire do <step>`](/reference/cli/commands/aspire-do/)| A named step and its dependencies | Run a specific step directly |
67
67
68
-
Ifnoresourcecontributesworkfora given entry point, Aspire can still run the pipeline successfully as a no-op. That usually means your AppHost hasn't added a target or other resource that contributes steps for that path yet.
68
+
If no resource contributes work for `publish` or `deploy`, Aspire has nothing to execute for that entry point. In current Aspire CLI builds, that entry point completes as a no-op. That usually means your AppHost hasn't added a target or other resource that contributes steps for that path yet.
69
69
70
70
These are separate entry points. Use `aspire publish` when you want a one-way handoff out of Aspire: it emits artifacts that another tool or a manual step will apply later. Use `aspire deploy` when you want Aspire to stay in control, generate the target-specific output behind the scenes, resolve parameter values, and apply the deployment in one operation. `aspire deploy` does not consume previously published assets.
71
71
@@ -104,11 +104,11 @@ var apiKey = builder.AddParameter("apiKey", secret: true);
-`apiKey` is the Aspire parameter name in the AppHost.
134
134
-`API_KEY` is the environment variable the deployed app receives.
135
135
-`Parameters__apiKey` is an environment variable you can use to supply the value to the AppHost when the pipeline runs.
136
+
-`APIKEY` is the publish-time placeholder name Docker Compose emits in generated `.env` and `${...}` references.
136
137
137
138
When the Docker Compose target publishes artifacts, the publish path preserves that relationship in target-specific output:
138
139
@@ -149,6 +150,8 @@ services:
149
150
APIKEY=
150
151
```
151
152
153
+
In this Docker Compose output, the placeholder name is `APIKEY` rather than `API_KEY`. The app still receives `API_KEY`; `APIKEY` is only the generated publish-time placeholder that the emitted artifacts use later.
154
+
152
155
The placeholder name in published output is target-specific, but the mapping stays the same:
0 commit comments