-
Notifications
You must be signed in to change notification settings - Fork 356
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
Devenv init template support #1718
Comments
I created a really simple implementation. May I ask why you don't just use |
Fantastic, thanks for working on this!
I just assumed it wouldn't work with devenv. In particular devenv's default mode, with Flake inputs defined in Since you created a PR, I'm assuming you see the value in having the template parameter on |
I made a quick example. You can use it with:
I don't really see any benefit, other than a simpler interface. In your documentation you would also have to add edit: I updated the example with a |
Thank you so much for the pointer and example! I didn't know it was even possible to use Flakes in that way. The
Yeah, that's pretty-much it. But, even knowing about
|
Problem
I'm developing drupal-devenv, which builds on devenv to provide Drupal development environments.
I feel the Getting Started process is less than ideal, users have to run
devenv init
, then edit our repo into their project's inputs and add the corresponding import. If you're new to devenv, this is all a bit opaque and gives a first impression that it requires a lot of boilerplate.Meanwhile, the competition is ddev, where getting started is
ddev config
followed byddev start
. While the config step does ask some questions, the whole process is short and streamlined.Solution
If we could provide a template for use with
devenv init
, with pre-configured inputs and such, users could get started just as easily as with ddev. For example, the usage might look like:Then users just have to run
devenv up
to get a fully working Drupal development environment.Related: #1705
The text was updated successfully, but these errors were encountered: