sailfork / t3code-github / .repos/ alchemy-effect/ website/ src/ content/ docs/ cli/ deploy.mdx

import Terminal from "../../../components/Terminal.astro";
alchemy deploy [options]

deploy computes a plan, asks for approval, and creates/updates/deletes resources to match the desired state.

<Terminal content={`[u]Plan[/u]: [g]2 to create[/g]

[g]+[/g] [b]Bucket[/b] d[/d] [g]+[/g] [b]Worker[/b] d[/d] [c](1 bindings)[/c] [s2][g]+[/g] [c]Bucket[/c]

Proceed? ◉ Yes ○ No [g]✓[/g] [b]Bucket[/b] d[/d] [g]created[/g] [g]✓[/g] [b]Worker[/b] d[/d] [g]created[/g] [s2][d]• Uploading worker (14.20 KB) ...[/d] [s2][d]• Enabling workers.dev subdomain...[/d] { [s2]url: "https://myapp-worker-dev-you-abc123.workers.dev", }`} />

On subsequent deploys, only changed resources are updated:

<Terminal content={`[u]Plan[/u]: [y]1 to update[/y]

[y]~[/y] [b]Worker[/b] d[/d]

Proceed? ◉ Yes ○ No [g]✓[/g] [b]Worker[/b] d[/d] [y]updated[/y] [s2][d]• Uploading worker (15.10 KB) ...[/d] { [s2]url: "https://myapp-worker-dev-you-abc123.workers.dev", }`} />

When the plan contains no changes, the approval prompt is skipped automatically.

Flags

OptionDescription
--config, -c <file>Stack file to deploy (defaults to alchemy.run.ts)
--stage <name>Stage to deploy to (defaults to $ALCHEMY_STAGE or live_$USER)
--yesSkip the approval prompt
--dry-runShow the plan without applying (same as alchemy plan)
--detailedShow declared resource properties as YAML
--forceForce updates for resources that would otherwise no-op
--adoptAdopt pre-existing cloud resources that conflict with this stack instead of failing. Useful for re-importing into a fresh state store.
--profile <name>Auth profile to use (defaults to $ALCHEMY_PROFILE or default)
--env-file <path>Load environment variables from a file

How --adopt decides what to take over is covered in Adopting Resources.

--dry-run runs the exact same code path as alchemy plan — see that page for the plan output format.

--detailed adds the YAML property view to the approval prompt, --yes deploys, and --dry-run previews.

Examples

# Deploy to production, skip the prompt
alchemy deploy --stage prod --yes

# Deploy a PR preview environment
alchemy deploy --stage pr-42

# Deploy a different stack file
alchemy deploy --config stacks/github.ts

# Preview what would change
alchemy deploy --dry-run

# Review declared inputs as YAML before applying
alchemy deploy --detailed

# Re-import existing cloud resources into a fresh state store
alchemy deploy --adopt

Where next