CLI deploy command
The trigger.dev deploy command can be used to manually deploy.
Run the command like this:
It performs a few steps to deploy:
- Optionally updates packages when running locally.
- Typechecks the code.
- Compiles and bundles the code.
- Checks that environment variables are set.
- Deploys the code to the cloud.
- Registers the tasks as a new version in the environment (prod by default).
You can also setup GitHub Actions to deploy your tasks automatically.
Options
Defaults to prod but you can specify staging.
Skips the pre-build typecheck step.
Skip checking for @trigger.dev package updates.
The platform to build the deployment image for. Defaults to linux/amd64.
The log level to use (debug, info, log, warn, error, none). Defaults to log.
The name of the config file, found where the command is run from. Defaults to trigger.config.ts.
The project ref. Required if there is no config file.
Self-hosting
These options are typically used when self-hosting or for local development.
Load the built image into your local docker.
Builds and loads the image using your local docker. Use the --registry option to specify the registry to push the image to when using --self-hosted, or just use --push to push to the default registry.
This option is coming soon. The registry to push the image to when using —self-hosted.
When using the —self-hosted flag, push the image to the default registry. (defaults to false when not using —registry)
This option is coming soon. Specify the tag to use when pushing the image to the registry.
Was this page helpful?