Repository navigation
fix: compte administrateur, seed haché et API sans hash (#189) - #190
Merged
Merged
Conversation
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.
Corrige #189.
Changements
prisma/seed.jshacheADMIN_PASSWORD. Le compte créé peut se connecter, ce qui retire la raison d'être du contournement du README.await» et lien vers bcrypt.fr supprimés, installations locale et de production réécrites..env.exampleremplace.default, supprimé par 87747ef.migratereçoit.env, nécessaire pour lancer le seed dans le conteneur.server/utils/publicUserFields.ts: liste unique des champs renvoyés parGET,POSTetPUTsur les utilisateurs. Le hash et le jeton ne sortent plus de ces routes.Vérification
Installation neuve, commandes du README exécutées telles quelles, base vide, mot de passe aléatoire :
migrate, seed etup -d --build appréussis. La base contient 1 admin avec un hash bcrypt et 19 tâches.npm install,prisma generate,migrate deployetdb seedréussis, même contenu de base.Effet en production
Aucun sur la base : le seed ne tourne qu'à l'installation. Le changement de l'API prendra effet au prochain déploiement.