Add manual setup checks for self hosted deployments

Offen
#153 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
docker, node.js, postgresql, typescript

Rechercherichtung

Start with the linked work in #157 and #158 to trace dependency checks and the dashboard flow, then identify the backend entry points for Cloudflare Workers and Node/Docker. Read the setup and operations documentation and inspect existing tests for both runtimes. Done means operators can run checks manually, understand passed, failed, or unavailable results, and PostgreSQL checks never keep a serverless database awake.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement good first issue help wanted

Goal

Give self hosted Codra operators a simple way to find setup and service problems without requiring any service, especially a serverless PostgreSQL database, to stay awake all the time.

What the check should cover

Check GitHub App setup, webhook delivery information, model provider credentials, the configured queue or worker, and PostgreSQL when the current runtime can check them. A result should say whether a check passed, failed, or could not be checked, and give a useful next step.

Serverless PostgreSQL requirement

Run a PostgreSQL check only when an operator asks for it or when Codra already needs a database connection for normal work. Let an ordinary connection attempt wake a suspended database. Do not poll it on a timer, keep a connection open to prevent suspension, or call it unhealthy only because it was idle. Explain cold start delays or timeouts when they can be identified.

Work breakdown

Done when

  • Operators can run checks manually and understand each result.
  • Checks are available in both Cloudflare Workers and Node/Docker where the runtime can support them.
  • A service the runtime cannot check is shown as unavailable, not failed.
  • PostgreSQL is never kept awake by health checks.
  • Setup and operations documentation explains the checks and their on demand behavior.

Before closing

  • npm run typecheck, npm test, and npm run lint all pass.
  • Backend checks work in both Cloudflare Workers and Node/Docker.
  • Tests cover the changed behavior in each affected runtime.
Vorherrschende Sprache
TypeScript
Sterne
125
Forks
23
Ø Merge
2 T. 13 Std.
Gemergte PRs (30 T.)
12

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus devarshishimpi/codra

Alle Issues in devarshishimpi/codra

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.