Repository navigation
feat: Proposition de stack de dev local full docker. - #446
Open
guillaume-a wants to merge 1 commit into
Open
guillaume-a wants to merge 1 commit into
guillaume-a wants to merge 1 commit into
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.
Proposition d'amélioration de la stack de dev local en full docker.
La stack actuelle part du principe que Node, PHP et Symfony CLI sont installés sur la machine du dev.
Or, ce n'est pas forcément le cas.
A titre perso, je n'ai pas tout cela sur ma machine. Je ne passe que par du docker.
Cette proposition ajoute un Dockerfile avec un PHP 8.5 Cli + composer + symfony cli et un autre conteneur pour node.
L'avantage est que cela fonctionne OTB via un
make initLe seul pré-requis devient d'avoir docker sur sa machine.
Lors du make init j'ai eu un soucis avec le faker
containerEnvironmentsUsage(...)Cette PR à également un fix dans la fixture
response.yml