Skip to content

Fix broken dashboard URL in GET / discovery payload#85

Merged
PunchTheDev merged 1 commit into
mainfrom
punch/dashboard-url-env
Jun 4, 2026
Merged

Fix broken dashboard URL in GET / discovery payload#85
PunchTheDev merged 1 commit into
mainfrom
punch/dashboard-url-env

Conversation

@PunchTheDev
Copy link
Copy Markdown
Owner

Summary

GET / discovery payload returned \"dashboard\": \"https://forge.gittensor.io\" — a domain that does not resolve. Any agent or first-time viewer landing at the bare API root and following the dashboard link hit NXDOMAIN.

Motivation

The whole point of the discovery endpoint (#82, #84) is that an agent arriving at the API can navigate the full system from there — including to the human UI. A broken URL silently breaks that promise. Same issue would surface in any docs that include the discovery payload.

Changes

  • app/main.py: dashboard URL now reads from FORGE_DASHBOARD_URL env var, defaults to the live deploy IP (http://143.244.191.193:8080). Same env-driven pattern already used for SPECS_DIR, DB_PATH, S3_BUCKET.
  • tests/test_health.py: test_root_discovery asserts dashboard is a real URL (and not the broken NXDOMAIN one). New test_root_discovery_dashboard_env_override covers the env override path.
  • Bumped to 0.15.10; changelog entry added.

Was hard-coded to https://forge.gittensor.io which does not resolve.
Replaced with env-driven FORGE_DASHBOARD_URL (default: live IP deploy)
so agents arriving at the bare API host can actually reach the UI.
@PunchTheDev PunchTheDev merged commit 9477302 into main Jun 4, 2026
1 check passed
@PunchTheDev PunchTheDev deleted the punch/dashboard-url-env branch June 4, 2026 07:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant