I think there is a problem with vvv-init.sh.

In nginx.conf template for custom site there is this line:

However, in vvv-init.sh the substitution is attempted on a different variable name:

So my guess is, variable name should be changed in either file.

Note: I have tried to make the change into vvv-init-sh and it worked. I can submit the code if you want me to.

I wonder if multisite is enabled and another flag is set say multisite_create: true, if you define other domains in the VVV config, it should go away and create those sites for you.

See #4

Do we need to update this? A utility was added to VVV 2 named trusted-hosts that does the same thing

I wonder if we could have the provisioner check a live site or an API in order to figure out some of the config options in advance? Maybe then we could auto-generate copy paste for the config file in the Go client facing admin when that arrives?

support is there but it could be clearer

The init for the sites creates the constant of VIP_GO_ENV. It makes it a dev value, which is a neat idea, but it a breaking change. Much of mine and many other's code checks to see if VIP_GO_ENV is defined and does different logic. If this constant is in place on local, this could mean production code that is not designed to run in local code will run and may break local installs.