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
{{ message }}
Repository navigation
Commit a3869e8
Browse filesBrowse the repository at this point in the historyBrowse files
docs: fix inaccuracies in CLI, config and deployment pages
Corrects the CLI, config, deployment and troubleshooting docs where they
had drifted from the CLI and SDK.
- CLI commands: adds missing options and arguments for `init`, `dev`,
`deploy`, `promote`, `login`, `whoami`, `update`, `projects` and `env`
(including `--branch` for preview environments), fixes wrong defaults,
and renames `--force-local-build` to `--local-build`.
- Build extensions: adds the missing extensions to the overview, fixes
the Python `requirements` option, the Prisma binary target, Puppeteer
imports and examples, and the `syncEnvVars` context and options.
- Deployment: covers the GitHub integration as a deploy path, and points
the Vercel snippet at the official Vercel integration.
- Alerts, query and private networking: adds missing webhook fields,
Query columns and tables, and fixes setup details.
- Fixes broken links and anchors across these pages and a few guides.
Mono-RevId: ce51189e8fc1d41ad566db57609f162b85c1e6a3
These commands manage environment variables on a project environment. They default to `prod`. Use `--env staging` or `--env preview` (with `--branch`) for the other environments. There is no `dev` target: local `trigger dev` reads your local `.env`.
Writes the project's environment variables to a local file. Defaults to `.env.local`. Fails if the file already exists unless you pass `--force`.
84
+
Writes the project's environment variables to a local file. Defaults to `.env.local`. Asks you to confirm before overwriting an existing file unless you pass `--force`. `TRIGGER_` system variables are omitted.
Path to a `.env` file to read `TRIGGER_PROJECT_REF` from. Defaults to `.env`, `.env.development`, `.env.local`, `.env.development.local` and `dev.vars` in the current directory.
The extension installs Chrome and sets `PUPPETEER_EXECUTABLE_PATH=/usr/bin/google-chrome-stable` for deployed builds automatically, so you do not need to set it. Don't set it in your Dev environment: the extension does nothing in Dev, and locally Puppeteer uses the browser it downloads on install.
29
27
30
28
Follow [this example](/guides/examples/puppeteer) to get setup with Trigger.dev and Puppeteer in your project.
0 commit comments