ops: align the production frontend with the canonical repository

Offen
  • Stimmt etwas nicht?
#74 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
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
next.js, typescript
Bereich
devops, web-dev

Rechercherichtung

Start by checking the existing Vercel project's GitHub connection, production branch, project root and build configuration, then confirm which reviewed commit serves the production domain. Deploy current main through that project and verify /practice, /learn, /api/platform/auth/session, About content, robots, sitemap and canonicals against the deployed commit. Record the commit and smoke-test outcome without exposing secrets, and document the reconnection and verification procedure in the deployment guide.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug

Observed on 2026-11-10

  • https://procoderji.com/practice, /learn and /api/platform/auth/session return 404.
  • /about returns 200 with the older "About ProCoderJii Notes" content/title.
  • These student routes and the account-session fallback already exist on canonical main (7d20d370269f938ee42058f6b9364b4e0351115e).
  • The latest Production deployment recorded through this repository's GitHub deployments API is dated 2026-11-02.

This suggests the public frontend does not reflect current main. Verify the actual hosting project and deployment source before assuming the exact cause.

Scope

  • An authorized operator checks the existing Vercel project's GitHub connection after repository transfer, production branch, project root and build configuration.
  • Confirm which reviewed commit is actually serving the production domain, then deploy current main through that existing project.
  • Verify the canonical site origin and keep credentials in the host's secret store.
  • Document the repository-transfer/reconnection and production verification procedure in the deployment guide.
  • Keep frontend deployment separate from provisioning the optional .NET service or Neon credentials. Guest practice must work without those services.
  • Any new spending, domain/DNS changes or external access grants need the owner's existing authorization.

Done when

Production serves /practice and /learn with 200, and /api/platform/auth/session returns its documented JSON (including the unconfigured-account fallback when appropriate). About content matches the deployed reviewed commit. Verify robots/sitemap/canonicals and record the deployed commit and smoke-test outcome without exposing secrets.

Completing this requires access to the existing hosting project; passing repository CI alone does not establish a successful production deployment.

Vorherrschende Sprache
TypeScript
Sterne
1
Forks
1
Ø Merge
8 Std. 58 Min.
Gemergte PRs (30 T.)
37

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 procoderji-com/procoderji

Alle Issues in procoderji-com/procoderji

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

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