deploy.sh: honour TG_POST_DEPLOY on the compose path too #109
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Jinemi/thermograph#109
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/post-deploy-gate-compose"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Third defect caught by actually running the cutover.
The per-environment gate on the post-deploy city warm and IndexNow ping went into
deploy/stack/deploy-stack.sh(beta, prod) but was missed indeploy.sh's compose branch — which is the single environment where the ungated default is wrong: dev.Standing dev up on vps1 therefore:
http://10.10.0.2:8137— a WireGuard address no crawler can reach.IndexNow rejected the batch (site verification incomplete) and the warm was rate-limited after six cities, so real spend was negligible — but that was luck, not design, and the warm was still running until dev's backend was restarted to stop it.
Verified after the fix:
Defaults to
1when unset so a checkout predatingenv-topology.shbehaves exactly as before.