Repository navigation
v2.1.7
Docs only. Reader round 7: fourteen places where two docs stated different facts.
- Circuit breaker: the README says 5 consecutive failures by default (
git_deploy_cb_max_failures).bay buildtakes the fleet from--fleetorBAY_FLEET, not from the directory you stand in. - Prune cron: every doc names
docker system prune -af --volumesand says it keeps named volumes (on Docker Engine 23 and later it removes only anonymous ones), so--data keepandbay removevolumes stay. - "Full deploy" is gone: the docs say "
bay deploy <env>with no--tags" for the untagged run, and "every deploy that reaches the container pass" for the.prev.jsonrotation. deploy-receipt.md names the verbs that rotate it. - Webhook: the hook URL is
https://<webhook domain>/webhook/<container name>.bay deploy <env>installs the receiver and trigger and makes the deploy key on the box; you add the key to GitHub.bay webhookis marked as the v1 form. services.ymlis generated: install.md, layout-scenarios.md and onboarding.md no longer tell you to edit it or copy it fromexample/.- Multi-region: a deploy aimed at a group writes
<group>.json, whichbay statusandbay plando not read. Usebay deploy <env> -- --limit <group>. - Quick start: commit the new fleet before
bay init. install.md says whatbay fleet initwrites. - bay-toml.md:
dockerfileandcontextare relative to the repo root,track = "pin"holds each push withbuild.held, and the old mounts fallback stays until a release removes it. plan.md states WANTED as two cases.