fix: use DNS for registry/beacon defaults in install.sh (PILOT-330)#189
fix: use DNS for registry/beacon defaults in install.sh (PILOT-330)#189matthew-pilot wants to merge 1 commit into
Conversation
Replace hardcoded IP 34.71.57.205 with registry.pilotprotocol.network for both REGISTRY and BEACON defaults. DNS makes server address mutable without requiring client re-installation.
|
🤖 Hank — CI status Classification: The build/test failure is a genuine code defect:
@matthew-pilot — fix or comment. Auto-classified at 2026-06-02T15:28:00Z. Re-runs on next push or check completion. |
🦾 Matthew PR Status — #189Title: fix: use DNS for registry/beacon defaults in install.sh (PILOT-330) TicketsLabels
Files Changed
Next Actions
🦾 Auto-generated status check by matthew-pr-worker |
🦾 Matthew PR Explain — #189What this PR doesfix: use DNS for registry/beacon defaults in install.sh (PILOT-330) Scope
TicketsFiles
Review Notes
🦾 Auto-generated explain by matthew-pr-worker |
🤖 Matthew — Canary Retry (PILOT-330)Verdict: ✅ RESOLVED — CI self-healed
Previously detected Auto-checked at 2026-05-31T20:05Z |
|
📊 PR Status — PILOT-330 PR is open ✓, mergeable ✓, not a draft. Labeled Ready for review — no blockers detected. |
What
Replace hardcoded IP
34.71.57.205with DNSregistry.pilotprotocol.networkfor REGISTRY and BEACON defaults in install.sh.Why
If the production server moves, every preinstalled client breaks until upgraded. Using DNS makes the address mutable — only the DNS record needs updating.
Changes
install.sh: 2 lines (+2/-2)Ticket
🔗 https://vulturelabs.atlassian.net/browse/PILOT-330