Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Admin Console] Ops visibility panels (mirror, workers, NIP-05, storage)

Abierto
#816 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@Ferryx349 ya está trabajando en esto.

Desde el 12/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Admin Console enhancement

Parent

Part of #688

Context

Operators have Network Health (#798, #800) and live metrics, but cannot inspect mirroring, background workers, NIP-05 verification, or storage counts from admin without SSH/SQL.

Goal

One admin Operations area covering mirror health, worker ops, NIP-05 visibility, storage counts, and Tor/I2P labeling, same auth, IP allowlist, and rate limits as other admin routes.

Scope

Backend — instrumentation
  • Publish bounded mirror state from static-mirroring workers (connection state, reconnect count, sanitized last error, last event time, target URL/index) via Redis/cache with TTL/heartbeat.
  • Publish bounded worker state for maintenance, relay-monitor, and summary of configured workers (from primary and/or per-worker heartbeats): type, index, last run start/finish, sanitized last error, enabled/disabled from settings.
Backend — APIs
  • GET /admin/ops/mirrors
  • GET /admin/ops/workers
  • GET /admin/ops/nip05-verifications — paginated; filters: domain, verified, min failures, stale vs nip05.verifyExpiration
  • POST /admin/ops/nip05-verifications/:pubkey/reverify — rate limited; same semantics as maintenance re-verify
  • GET /admin/ops/storage/counts — kinds, since, until; repository counts aligned with NIP-45 semantics; bounded (timeout, max window, cost limits)
Dashboard
  • New Operations nav view (or equivalent) with panels: Mirror Health, Worker Ops, NIP-05, Storage counts
  • Tor/I2P: show probe networkType / DNS-skip notes (cross-link Network Health where useful; no duplicate probe engine)
Lenguaje dominante
TypeScript
Estrellas
829
Forks
234
Merge medio
2 d 10 h
PR fusionados (30 d)
24

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cameri/nostream

Todos los issues de cameri/nostream

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.