ops: align the production frontend with the canonical repository

Ouverte
  • Quelque chose ne va pas ?
#74 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
35/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
next.js, typescript
Domaine
devops, web-dev

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
1
Forks
1
Merge moyen
8 h 58 min
PR mergées (30 j)
37

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de procoderji-com/procoderji

Toutes les issues de procoderji-com/procoderji

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.