ops: align the production frontend with the canonical repository

Aperta
  • Qualcosa non va?
#74 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
next.js, typescript
Ambito
devops, web-dev

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
1
Fork
1
Merge medio
8h 58m
PR unite (30g)
37

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di procoderji-com/procoderji

Tutte le issue di procoderji-com/procoderji

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.