Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
#816 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@Ferryx349 já está trabalhando nisso.

Desde 12/10/2026.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

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)
Linguagem predominante
TypeScript
Estrelas
829
Forks
234
Merge médio
2d 10h
PRs com merge (30d)
24

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de cameri/nostream

Todas as issues de cameri/nostream

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.