Repository navigation
Passage de MongoDB à PostgreSQL - #143
Merged
Merged
Conversation
- Prisma et Payload sur PostgreSQL (add-on Clever Cloud), migrations Payload versionnées - script de reprise des données depuis MongoDB (yarn migrate:mongo-to-postgres) - route /api/health pour le healthcheck Clever - cache serveur des données publiques et requêtes d'agrégation allégées - corrections diverses
alo-is
force-pushed
the
feat/migration-postgresql
branch
from
October 20, 2026 16:00
1362f5e to
294393f
Compare
Aucun test ni audit Lighthouse n'est lancé (jobs commentés dans la CI). Retire aussi extract-zip et sprintf-js, remontés par Dependabot.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On quitte le MongoDB externe pour l'add-on PostgreSQL managé de Clever Cloud (l'add-on MongoDB de Clever est bloqué en 4.0.3, sans transactions, donc inutilisable avec Prisma et le driver actuel).
Ce qui change
postgresql(schémapublic), Payload passe sur@payloadcms/db-postgres(schémapayload,push: false, migrations danssrc/migrations)nullde Mongo pour ne pas changer l'affichagePRISMA_CONNECTION_LIMIT,PAYLOAD_DB_POOL_MAX)/api/healthpour le healthcheck Clever (CC_HEALTH_CHECK_PATH=/api/health)Reprise des données
yarn migrate:mongo-to-postgreslit les deux bases Mongo (MONGO_SOURCE_URI) et écrit dans PostgreSQL. Options :--dry-run,--reset. Le script compare les volumes à la fin.Testé sur une copie de la prod : mêmes volumes, réponses d'API identiques à la prod (hors ordre alphabétique des accents et ids Payload devenus numériques). Un env de recette tourne dessus avec les données de prod.
Mise en prod
NEXT_PUBLIC_SERVER_URL,CC_HEALTH_CHECK_PATH,MONGO_SOURCE_URI(le temps de la reprise)yarn payload migrateetyarn prisma db push), puis lancer la reprise depuis l'instanceMONGO_SOURCE_URIet les anciennes variables MongoVoir le README pour le détail et le setup local (
docker compose up).