Skip to content

Deploy each script with all its files and record it per script #148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adriaandotcom merged 5 commits into from
Oct 29, 2026
Merged

Deploy each script with all its files and record it per script #148

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
abf4dfe
Deploy each script with all its files and record it per script
Oct 28, 2026
cf52756
Record each script separately and keep deploys working without history
Oct 28, 2026
1c51e1f
Retry GitHub reads without a stale token and document GH_TOKEN
Oct 29, 2026
8ad1321
Don't offer draft releases
Oct 29, 2026
7dc3cbf
Merge branch 'main' into codex/deploy-script-groups
adriaandotcom Oct 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ pnpm run deploy

The interactive CLI starts in dry-run mode by default. You pick a release (the newest by default), and the CLI downloads its `scripts-vN.tar.gz` and checks the file against the SHA-256 digest GitHub recorded. It then shows the release each destination runs now, every affected path, and the first-line script-header diff. It never builds or reads local `dist/` files. Choosing a real deployment requires a clean repository and a second confirmation. To roll back, deploy an older release; published SRI files are never overwritten.

After a real deployment that includes `latest.js`, the CLI records a GitHub deployment for each destination (`cdn` and `custom-domains`), so [Deployments](https://github.com/simpleanalytics/scripts/deployments) shows what is live. Deployments of only auto-events, SRI or light aren't recorded, because the destination keeps running its recorded release. It runs `gh`, or the command in `DEPLOY_GH_COMMAND`.
You choose the scripts (the default embed script with all its files: latest, SRI, light and proxy; and/or auto-events) and the destinations (CDN and/or Caddy). After a real deployment, the CLI records a GitHub deployment per script and destination (`cdn`, `custom-domains`, `cdn-auto-events` and `custom-domains-auto-events`), so [Deployments](https://github.com/simpleanalytics/scripts/deployments) shows what is live. It runs `gh`, or the command in `DEPLOY_GH_COMMAND`. Set `GH_TOKEN` or `GITHUB_TOKEN` in `.env` so reading that history doesn't hit GitHub's unauthenticated rate limit.

CDN writes use `BUNNY_SCRIPTS_ACCESS_KEY` and `BUNNY_SCRIPTS_ACCOUNT_KEY` from `.env`. Caddy reads and writes require SSH access to `user@esapp05.simpleanalytics.com`.

Expand Down
Loading
Loading