The trigger.dev deploy
command can be used to manually deploy.
You run the command like this:
It performs a few steps to deploy:
--env
or -e
Defaults to prod
but you can specify staging
.
--skip-typecheck
or -T
Skips the pre-build typecheck step.
--build-platform
The platform to build the deployment image for. Defaults to linux/amd64
.
--log-level
or -l
The log level to use (debug, info, log, warn, error, none). Defaults to log
.
--config
or -c
The name of the config file, found where the command is run from. Defaults to trigger.config.ts
.
--project-ref
or -p
The project ref. Required if there is no config file.
These options are usually only relevant to self-hosters or for local development.
--skip-deploy
or -D
Load the built image into your local docker.
--self-hosted
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-image
to push to the default registry.
--registry
The registry to push the image to when using —self-hosted.
--push-image
When using the —self-hosted flag, push the image to the default registry. (defaults to false when not using —registry)
--tag
Specify the tag to use when pushing the image to the registry.