Use next standalone mode #856
Open
Conversation
This file contains 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
totakoko
force-pushed
the
improve_scalingo_memory
branch
from
dcb0881
to
7c33c2b
Compare
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.
La PR utilise le mode standalone de Next pour réduire la taille de l'image, car Scalingo n'aime pas quand ça fait + de 1.5Go (limite à 2Go actuellement).
Sauf que le mode standalone ne package pas les dépendances node_modules.
Et donc on se retrouve avec 2 choses qui ne fonctionnent pas :
Idéalement, il faudrait avoir un point d'entrée sur l'appli (pour la compilation) qui permet de démarrer le serveur web, lancer le cron ou appliquer les migrations.