oxyc

> Also, note that I think I'd like to include #1332 in a 4.x release, but I'm considering saving this change (along with more of a "this is how you...

Regarding docs for this I guess we could entirely delete _Drupal VM as a Composer Dependency_, or move it as a brief page under_Getting Started_ section somewhere. In the Installation...

Maybe add as the first page _Installation / How to integrate Drupal VM_ (I'm terrible at naming things) Where we point out that there are two ways of integrating Drupal...

> that's probably going to still be the default/majority use case for a while Yeah this would probably still be the first option mentioned in docs. What about the Quick...

Do we want to add support for storing configuration values in the `composer.json` [like beetbox](https://github.com/thom8/drupal8-vagrant/blob/master/composer.json#L27)? We could either a) scaffold the file like they do or b) merge it into...

> we decided to let config in composer.json overwrite the normal config file so it wasn't possible to manage config in both places, mainly to reduce the WTF factor... Yeah...

@fubarhouse do you have any example of your setup that you could post?

Thanks! Looks pretty easy to setup. And saw the the config allows multiple `log-files` so that's easy. Then just a simple systemd service to keep it running. Main issue I...

I especially like the ability to tell users in the issue queue to run `DRUPALVM_DEBUG=v vagrant up`

> My main question is what does the debug .cfg file provide over the normal one? It seems like it would just be the first few messages at the top...