stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Make the deployed mobile dashboard reachable through authenticated readiness #1048

New Issue
Closed
opened 2026-08-17 23:23:39 +00:00 by timmy · 0 comments
timmy commented 2026-08-17 23:23:39 +00:00
Owner
Copy Link

Evidence

The production process is live but every operator entry route is blocked before UI render: /dashboard/ and /dashboard/login return 503 Dashboard authentication is not configured; /dashboard/readyz also returns 503 while /dashboard/healthz returns 200. Current systemd environment provides only Gitea connectivity, not dashboard operator authentication. No open issue is eligible for timmy, and historical titles cover canonical origin, subpath routing, and mobile home behavior but not restoring the deployed authenticated entry route.

User impact

A phone operator currently cannot reach sign-in, the mobile Home surface, install metadata, or any capture/work flow despite healthy process monitoring.

Scope

  • Add a deterministic deployment smoke verifier for the public subpath that distinguishes liveness from usable authenticated readiness.
  • Cover redirect/login HTML, PWA manifest scope/start URL, authenticated Home HTML, and secret-safe failure output.
  • Document secure operator service configuration and smoke invocation without committing credentials.
  • Configure the running service through a root-only environment file and verify the real /dashboard/ route.

Acceptance

  1. /dashboard/healthz and /dashboard/readyz return 200.
  2. Unauthenticated /dashboard/ reaches rendered sign-in rather than JSON/503.
  3. The manifest remains scoped under /dashboard/.
  4. An authenticated smoke request reaches the rendered dashboard Home and never prints the access token.
  5. Unit tests, full suite, packaged browser journeys, and Gitea Actions are green.
## Evidence The production process is live but every operator entry route is blocked before UI render: `/dashboard/` and `/dashboard/login` return 503 `Dashboard authentication is not configured`; `/dashboard/readyz` also returns 503 while `/dashboard/healthz` returns 200. Current systemd environment provides only Gitea connectivity, not dashboard operator authentication. No open issue is eligible for timmy, and historical titles cover canonical origin, subpath routing, and mobile home behavior but not restoring the deployed authenticated entry route. ## User impact A phone operator currently cannot reach sign-in, the mobile Home surface, install metadata, or any capture/work flow despite healthy process monitoring. ## Scope - Add a deterministic deployment smoke verifier for the public subpath that distinguishes liveness from usable authenticated readiness. - Cover redirect/login HTML, PWA manifest scope/start URL, authenticated Home HTML, and secret-safe failure output. - Document secure operator service configuration and smoke invocation without committing credentials. - Configure the running service through a root-only environment file and verify the real `/dashboard/` route. ## Acceptance 1. `/dashboard/healthz` and `/dashboard/readyz` return 200. 2. Unauthenticated `/dashboard/` reaches rendered sign-in rather than JSON/503. 3. The manifest remains scoped under `/dashboard/`. 4. An authenticated smoke request reaches the rendered dashboard Home and never prints the access token. 5. Unit tests, full suite, packaged browser journeys, and Gitea Actions are green.
timmy self-assigned this 2026-08-17 23:23:39 +00:00
timmy closed this issue 2026-08-17 23:38:24 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#1048
No description provided.
Delete Branch "%!s()"

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?