Tom J Nowell

On the frontend of my site it would appear to be `jetpack_css`, but that may be due to micro-optimising shenanigans I did Here's the kludge I tested it with: ```php...

```php if ( is_bool( $dependency ) ) { continue; } ``` This would fix the issue though it would be useful to know that something named `jetpack_css` was deregistered

hmmm this is in production so I'm not keen on installing node/npm/grunt/etc to build the `develop` branch. To reproduce, I have this mu-plugin: ```php

@srg9000 There's information here we didn't get over at VVV, it looks like the VM didn't boot within a timeout threshold, so the SSH timed out and Vagrant crashed during...

@osy @ktprograms you're best looking at the parallels provider as an example. However some finer details I can foresee the following: - a vagrant plugin will need to be built...

@neonihil I believe that the open questions at the moment are from the UTM side, e.g. you could create a vagrant provider for UTM but knowing how to configure UTM...

Doesn't look like it, but you shouldn't need `vv` to change this, and you shouldn't be using `vv` with VVV 2+ it doesn't fully support it. Instead, add the new...

@gleatherman there's https://varyingvagrantvagrants.org/docs/en-US/troubleshooting/vv/ but it's not exactly a step by step guide. `vv` doesn't create sites the way it's supposed to, even on VVV 1. E.g. in VVV 1 you...

`vv` doesn't fully support VVV 2, do not use it Instead, add the host to `vvv-custom.yml` and reprovision, e.g. ``` mysite: hosts: mysite.test mysite.com ```

For it to work properly without problems in the future it would need to be totally rebuilt, it never really worked correctly with VVV 1 to begin with due to...