Skip to content

Publish a status page and a known-issues notice #520

Description

@vidit-admin

Both answer "is it known, is the site up" for people outside the repo. (1) What's in flight. A pinned location for "yes, the X bug is known and being worked on": either a STATUS.md at the repo root (read by anyone clicking through to the source) or a pinned message in the Discord channel. Today the pattern is repeated explanation in DMs; pick a format when the same "is X being looked at?" question lands twice. (2) Branded status URL. UptimeRobot exposes a public status page on free tier (currently https://stats.uptimerobot.com/<monitor-id> for the Vidit API health monitor); the URL leaks the provider name and reads off-brand. A Cloudflare Redirect Rule on a status.vidit.app subdomain would 302 every visit to the underlying UptimeRobot URL; clean brand, no UptimeRobot upgrade needed. DNS: add a record for status.vidit.app and flip it to Proxied (orange cloud); safe to proxy this one because the subdomain hosts no service and doesn't need Let's Encrypt (unlike the apex and api. where proxy mode breaks cert provisioning, see engineering.md → Particularities). Cloudflare → Rules → Single Redirect: match http.host eq "status.vidit.app" → dynamic redirect to https://stats.uptimerobot.com/<monitor-id>, status 302. Free on all Cloudflare plans. Worth wiring once the status page becomes something analysts are asked to check; not urgent until then.

Imported from planning/backlog.md.

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions