Run prettier across the repo, exclude the lockfile from it
Prettier had never been run in --check mode here before, so this had drifted across most files (markdown tables, long option() chains, line wrapping). Purely formatting, no logic changes - needed so a CI format:check gate can actually pass. Adds .prettierignore for pnpm-lock.yaml specifically: prettier's YAML formatter rewrites every quoted key (single -> double quotes) producing an ~8700-line diff of pure noise on a file pnpm itself owns the formatting of. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Claude Sonnet 5
@@ -99,20 +99,20 @@ the script — always as a discrete argv element or env var, never interpolated
|
||||
|
||||
## CLI Usage
|
||||
|
||||
| Command | Description |
|
||||
|---|---|
|
||||
| `triggershell init [PATH]` | Scaffold a new config file + `.env` (`--port`, `--auth/--no-auth`, `--force`) |
|
||||
| `triggershell validate [-c CONFIG]` | Validate a config file against the full schema |
|
||||
| `triggershell start [-c CONFIG] [--port] [--host] [--no-browser]` | Run the web app |
|
||||
| `triggershell doctor [-c CONFIG]` | Print environment/config diagnostics |
|
||||
| `triggershell scripts list [-c CONFIG]` | List configured scripts |
|
||||
| `triggershell scripts show <scriptId> [-c CONFIG]` | Show a script's command and variables |
|
||||
| Command | Description |
|
||||
| --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `triggershell init [PATH]` | Scaffold a new config file + `.env` (`--port`, `--auth/--no-auth`, `--force`) |
|
||||
| `triggershell validate [-c CONFIG]` | Validate a config file against the full schema |
|
||||
| `triggershell start [-c CONFIG] [--port] [--host] [--no-browser]` | Run the web app |
|
||||
| `triggershell doctor [-c CONFIG]` | Print environment/config diagnostics |
|
||||
| `triggershell scripts list [-c CONFIG]` | List configured scripts |
|
||||
| `triggershell scripts show <scriptId> [-c CONFIG]` | Show a script's command and variables |
|
||||
| `triggershell run <scriptId> [--var name=value...] [--token] [--local\|--remote] [--no-wait]` | Run a configured script - through an already-running server's API if one is reachable (so any open browser tab sees it live), otherwise standalone. See [Running scripts from the CLI](#running-scripts-from-the-cli). |
|
||||
| `triggershell users add <username> [-c CONFIG] [--inline]` | Hash a password, store it in `.env`, and print a `${VAR}` snippet for `auth.users` (`--inline` prints the raw hash instead) |
|
||||
| `triggershell users add-token <name> [-c CONFIG] [--inline]` | Generate an API token, store its hash in `.env`, and print a `${VAR}` snippet for `auth.tokens` (`--inline` prints the raw hash instead) |
|
||||
| `triggershell service install [--system]` | Install a systemd unit that runs `triggershell start` (per-user by default, Linux only) |
|
||||
| `triggershell service uninstall [--system]` | Stop, disable, and remove the systemd unit |
|
||||
| `triggershell service status [--system]` | Show the systemd unit's status |
|
||||
| `triggershell users add <username> [-c CONFIG] [--inline]` | Hash a password, store it in `.env`, and print a `${VAR}` snippet for `auth.users` (`--inline` prints the raw hash instead) |
|
||||
| `triggershell users add-token <name> [-c CONFIG] [--inline]` | Generate an API token, store its hash in `.env`, and print a `${VAR}` snippet for `auth.tokens` (`--inline` prints the raw hash instead) |
|
||||
| `triggershell service install [--system]` | Install a systemd unit that runs `triggershell start` (per-user by default, Linux only) |
|
||||
| `triggershell service uninstall [--system]` | Stop, disable, and remove the systemd unit |
|
||||
| `triggershell service status [--system]` | Show the systemd unit's status |
|
||||
|
||||
### Running scripts from the CLI
|
||||
|
||||
@@ -154,20 +154,20 @@ Passwords are hashed with argon2id; only the hash ever lives in the config file.
|
||||
|
||||
Full reference with request/response shapes and curl examples: [`docs/API.md`](docs/API.md).
|
||||
|
||||
| Method | Path | Notes |
|
||||
|---|---|---|
|
||||
| GET | `/api/healthz` | Unauthenticated readiness probe |
|
||||
| POST | `/api/auth/login` | `{username, password}` → sets session cookie |
|
||||
| POST | `/api/auth/logout` | Clears the session |
|
||||
| GET | `/api/auth/session` | Current auth state |
|
||||
| GET | `/api/scripts` | List configured scripts |
|
||||
| GET | `/api/scripts/:scriptId` | Full script schema (variables, UI hints) |
|
||||
| POST | `/api/scripts/:scriptId/runs` | Start a run: `{variables: {...}}` |
|
||||
| GET | `/api/runs` | History: `?scriptId=&status=&limit=&cursor=` |
|
||||
| GET | `/api/runs/:runId` | Single run's status/metadata |
|
||||
| POST | `/api/runs/:runId/cancel` | Cancel an active run |
|
||||
| GET | `/api/runs/:runId/logs` | Full or tailed log output (`?tail=&download=`) |
|
||||
| WS | `/ws/runs` | Subscribe to a run's live output/status; send `cancel` |
|
||||
| Method | Path | Notes |
|
||||
| ------ | ----------------------------- | ------------------------------------------------------ |
|
||||
| GET | `/api/healthz` | Unauthenticated readiness probe |
|
||||
| POST | `/api/auth/login` | `{username, password}` → sets session cookie |
|
||||
| POST | `/api/auth/logout` | Clears the session |
|
||||
| GET | `/api/auth/session` | Current auth state |
|
||||
| GET | `/api/scripts` | List configured scripts |
|
||||
| GET | `/api/scripts/:scriptId` | Full script schema (variables, UI hints) |
|
||||
| POST | `/api/scripts/:scriptId/runs` | Start a run: `{variables: {...}}` |
|
||||
| GET | `/api/runs` | History: `?scriptId=&status=&limit=&cursor=` |
|
||||
| GET | `/api/runs/:runId` | Single run's status/metadata |
|
||||
| POST | `/api/runs/:runId/cancel` | Cancel an active run |
|
||||
| GET | `/api/runs/:runId/logs` | Full or tailed log output (`?tail=&download=`) |
|
||||
| WS | `/ws/runs` | Subscribe to a run's live output/status; send `cancel` |
|
||||
|
||||
## Development
|
||||
|
||||
@@ -199,7 +199,7 @@ See [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) for how the pieces fit togeth
|
||||
|
||||
- Scripts are always spawned with an argv array (`execa`), never a shell string — variable values
|
||||
can never inject additional shell commands. A script's own `command`/`args` may still use `shell:
|
||||
true` as an explicit, documented opt-in when the script genuinely needs pipes/globs; that
|
||||
true` as an explicit, documented opt-in when the script genuinely needs pipes/globs; that
|
||||
reintroduces shell interpretation of `passAs: arg` values, so prefer `passAs: env` for anything
|
||||
user-controlled in that case.
|
||||
- `secret: true` variables are masked in the UI and redacted from persisted run records; only the
|
||||
|
||||
Reference in New Issue
Block a user