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
* WIP creating a CLI section
* WIP adding more CLI commands in a new section
* New CLI section with introduction and more CLI commands
* More improvement to the CLI options
* Each CLI command has its own page
* fixed broken links
* Removed outdated copy
<Warning>Will fail in CI if any version mismatches are detected. Ensure everything runs locally first using the [dev](/cli-dev) command and don't bypass the version checks!</Warning>
27
-
28
-
It performs a few steps to deploy:
29
-
30
-
1. Optionally updates packages when running locally.
31
-
2. Typechecks the code.
32
-
3. Compiles and bundles the code.
33
-
4. Checks that [environment variables](/deploy-environment-variables) are set.
34
-
5. Deploys the code to the cloud.
35
-
6. Registers the tasks as a new version in the environment (prod by default).
36
-
37
-
You can also setup [GitHub Actions](/github-actions) to deploy your tasks automatically.
38
-
39
-
## Options
40
-
41
-
### Environment `--env` or `-e`
42
-
43
-
Defaults to `prod` but you can specify `staging`.
44
-
45
-
### Skip typecheck `--skip-typecheck` or `-T`
46
-
47
-
Skips the pre-build typecheck step.
48
-
49
-
### Build platform `--build-platform`
50
-
51
-
The platform to build the deployment image for. Defaults to `linux/amd64`.
52
-
53
-
### Log level `--log-level` or `-l`
54
-
55
-
The log level to use (debug, info, log, warn, error, none). Defaults to `log`.
56
-
57
-
### Set config filename `--config` or `-c`
58
-
59
-
The name of the config file, found where the command is run from. Defaults to `trigger.config.ts`.
60
-
61
-
### Set the projectRef `--project-ref` or `-p`
62
-
63
-
The project ref. Required if there is no config file.
64
-
65
-
### Self-hosted options
66
-
67
-
These options are usually only relevant to self-hosters or for local development.
68
-
69
-
#### Skip deploying the image `--skip-deploy` or `-D`
70
-
71
-
Load the built image into your local docker.
72
-
73
-
#### Self-hosted (builds locally) `--self-hosted`
74
-
75
-
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.
76
-
77
-
#### Registry `--registry`
78
-
79
-
<ComingSoon />
80
-
81
-
The registry to push the image to when using --self-hosted.
82
-
83
-
#### Push image `--push`
84
-
85
-
When using the --self-hosted flag, push the image to the default registry. (defaults to false when not using --registry)
86
-
87
-
#### Tag the image `--tag`
88
-
89
-
<ComingSoon />
90
-
91
-
Specify the tag to use when pushing the image to the registry.
9
+
<CliDeployCommands/>
92
10
93
11
{/* todo add options, remove the reference docs */}
It will first perform an update check to prevent version mismatches, failed deploys, and other errors. You will always be prompted first.
25
-
26
-
You will see in the terminal that the server is running and listening for requests. When you run a task, you will see it in the terminal along with a link to view it in the dashboard.
27
-
28
-
It is worth noting that each task runs in a separate Node process. This means that if you have a long-running task, it will not block other tasks from running.
29
-
30
-
## Options
31
-
32
-
### Attaching a local debugger
33
-
34
-
You can use the `--debugger` flag to run the server in debug mode. This will allow you to attach a debugger to the server and debug your tasks.
35
-
36
-
<CodeGroup>
37
-
38
-
```bash npm
39
-
npx trigger.dev@beta dev --debugger
40
-
```
41
-
42
-
```bash pnpm
43
-
pnpm dlx trigger.dev@beta dev --debugger
44
-
```
45
-
46
-
```bash yarn
47
-
yarn dlx trigger.dev@beta dev --debugger
48
-
```
49
-
50
-
</CodeGroup>
51
-
52
-
### Concurrently running the terminal
53
-
54
-
Install the concurrently package as a dev dependency:
The CLI log level to use. Options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This does not affect the log level of your trigger.dev tasks. Defaults to "log".
The CLI log level to use. Options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This does not affect the log level of your trigger.dev tasks. Defaults to `log`.
Sets the CLI log level. Available options are `debug`, `info`, `log`, `warn`, `error`, and `none`. This setting doesn't affect the log level of your trigger.dev tasks. The default is `log`.
0 commit comments