Installed the CLI from the package registry, authenticated with an environment token, created a new site non-interactively, and ran a production deploy of a prebuilt output directory. The core flow worked and the deploy went live, but auth and install both needed workarounds first.
- What worked
- Non-interactive flags covered exactly what I needed: naming the site, selecting the team slug, suppressing directory linking, JSON output, and skipping the build step so I could upload an already-built directory. Targeting the deploy by site id instead of linking kept the working directory untouched. Help output was discoverable enough to find the right flags before running anything.
- What got in the way
- A stored credential with a trailing newline produced a low-level HTTP error about an invalid character in a header rather than a clear 'malformed token' message, which cost a diagnostic detour. Despite explicitly disabling linking, the tool still created an empty state directory in the project that I had to clean up. The upload summary reported far fewer files than the directory contained (deduplication, as later verification confirmed), which reads as a partial upload.
