Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| The runner base keeps its old comment, so the pushed base image still matches its folder | 1 | #!/usr/bin/env bash |
| 2 | # Deploys g1t: every part, or the ones named, migrations first and then | |
| 3 | # stage by stage, as deploy/stack.jsonc orders them. A thin wrapper over | |
| 4 | # scripts/deploy.mjs, which can also deploy only what changed: | |
| 5 | # | |
| 6 | # scripts/deploy.sh # everything | |
| 7 | # scripts/deploy.sh billing web # just these, still in order | |
| 8 | # node scripts/deploy.mjs plan # what changed since each part's live commit | |
| 9 | # node scripts/deploy.mjs deploy # only that | |
| 10 | # | |
| 11 | # Uses your `wrangler login`. The repository's .env may hold a token for | |
| 12 | # other tools; it is ignored here unless you set CLOUDFLARE_DEPLOY_TOKEN. | |
| The docs folder is gone, and what it held lives where people read it: how a self-hosted g1t runs and how to deploy g1t to Cloudflare are pages on docs.g1t.sh under Run g1t yourself, and speed, rate limits and operating g1t.sh are sections of CONTRIBUTING.md; code that cited a file in docs/ now points to the page or section that covers it, or says what it means itself, and applied migrations and the runner images are left as they were. | 13 | # See docs.g1t.sh/guides/deploy-to-cloudflare/. |
| The runner base keeps its old comment, so the pushed base image still matches its folder | 14 | set -euo pipefail |
| 15 | ||
| 16 | ROOT="$(cd "$(dirname "$0")/.." && pwd)" | |
| 17 | if [ $# -eq 0 ]; then | |
| 18 | exec node "$ROOT/scripts/deploy.mjs" deploy --all | |
| 19 | fi | |
| 20 | names=$(IFS=,; echo "$*") | |
| 21 | exec node "$ROOT/scripts/deploy.mjs" deploy --force --only "$names" |
This file's history is long; its oldest lines are credited to the oldest commit read.