How it works
All the resources are deployed as concurrently as possible, based on their dependencies. For resources like your container images, sites, and functions; it first builds them and then deploys the generated assets. Since the build processes for some of these resources take a lot of memory, their concurrency is limited by default. However, this can be configured.| Resource | Concurrency | Flag |
|---|---|---|
| Sites | 1 | SST_BUILD_CONCURRENCY_SITE |
| Functions | 4 | SST_BUILD_CONCURRENCY_FUNCTION |
| Containers | 1 | SST_BUILD_CONCURRENCY_CONTAINER |
sst deploy. This is useful for CI environments where you want to control this based on how much memory your CI machine has.
For example, to build a maximum of 2 sites concurrently:
Options
--target
Only run it for the given component.
--exclude
Exclude the specified component from the operation.
--continue
Typically, this command exits when there’s an error deploying a resource. But sometimes you want to be able to continue deploying as many resources as possible:
--dev
The sst dev command deploys your resources a little differently. It skips deploying resources that are going to be run locally. Sometimes you want to deploy a personal stage without starting sst dev.
--dev flag will deploy your resources as if you were running sst dev.
--policy
Run policy pack validation against the preview changes.
Examples
Deploy to production
Deploy with policy validation
Deploy a specific component
Deploy everything except a component
Continue on error
Deploy as many resources as possible even if some fail:Deploy in dev mode
Deploy resources assst dev would:
Related
sst dev- Run your app in development modesst remove- Remove your deployed appsst refresh- Refresh your app state