-
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for extension using drupalpod.yaml file #115
Comments
Thank you @chrisfromredfin |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe
I would love the ability to add some extra enhancements to the "up and running" state of a DrupalPod instance. For example, when I'm using DrupalPod to develop my contrib module, there are some other modules I like to have to help me. I might be writing an add-on for Commerce, so I might want Commerce to come pre-installed or available in the repo, at it's latest -dev or stable verrsion.
Describe the solution you'd like
Support reading a contrib project's "drupalpod.yaml" file to provide some of the extra configuration.
Describe alternatives you've considered
I thought, well, I could just fork DrupalPod and make my own with my own scripts, but this seems like a useful feature to many module developers and contributors across the board -- being able to give contributors a known good "starting point" simplifies so much more of the process.
Additional context
https://drupal.slack.com/archives/C01N7HQSSFN/p1684339120557419
The text was updated successfully, but these errors were encountered: