feat(Local recipe starters): Create Repeatable Local Environment enhancement #840
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
* Adds scripts to init and destroy a local Drupal instance that will be ignored by vcs. * Initial scaffolding for a next-drupal recipe. Currently only installs next module.
* Create example consumer * Create example content * Use local version of Drupal module rather than packagist * Add drupal/core-dev to make running module tests possible * Add working versions of .env.local to starters
|
@joaogarin is attempting to deploy a commit to the Chapter Three Team on Vercel. A member of the Team first needs to authorize it. |
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.
This pull request is for: (mark with an "x")
examples/*modules/nextpackages/next-drupalstarters/basic-starterstarters/graphql-starter(not yet)starters/pages-starterGitHub Issue: #834
Describe your changes
I have pigybacked on https://github.com/chapter-three/next-drupal/tree/local-recipe to use the script based approach to setup ddev locally both for backend and frontend.
The idea here would be to spin up (and down) easily starterkits to improve contirbutions to the project and make it easier also to eventually run some end2end tests (this could easily be added to some CI like github actions to spinup ddev and run tests against)
Happy to get feedback here, or for someone else to use this and make it better..or drop it completely. this also helped me just understand the solution better (you can only get so far just by reading the code:P )
ddev init :
Spins up a new folder local-next-drupal and in it will use the ddev config which will spin up drupal and the frontend. The frontend will run using pm2
The script receives the starter and spins up the right starter accordingly (in it could also copy specific modules / recipes and enable them)
ddev destroy :
stops ddev and removes the folder