Rendre les images Docker reproductibles et plus sûres #14
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: jeux/le-grand-concours#14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problème
Le Dockerfile serveur n’utilise pas le lockfile et lance
npm install. Les conteneurs s’exécutent en root et aucun healthcheck n’est défini. La disponibilité des assets conditionne également le build client.Attendu
package-lock.jsonet utilisernpm ci --omit=devcôté serveur.Audit 2026-06-24 : verifier aussi le cas sans assets prives dans un checkout propre. Les assets ignores sous client/public ne doivent jamais etre requis par Vite au build. Garder les references runtime publiques ou fournir explicitement l'archive original en CI de release.