Ian Dunn

There's probably a few more that aren't jumping out at me, but: * Vagrant is slow * Only one HTTP server can use port `80`, so working on non-WME sites...

> The meta environment provisioner is unnecessarily complex, which is why it's slow. I was referring to things like TTFB, but that may have improved in the past few years....

@pattonwebz , I think @dd32 has tested out a Docker env for the theme directory specifically. That might help in the meantime, and could provide provision scripts, etc that WME...

For the Events API, there are some notes at these links: * https://wordpress.slack.com/archives/C02QB8GMM/p1508511323000272 * https://wordpress.slack.com/archives/C02QB8GMM/p1508511412000106 I think @metalandcoffee has some notes on getting it setup as well. I'll share some...

> Could you share the directory structure for the API and where the Plugins and Themes API would fit in as they are not yet open sourced? If I understand...

That's a really interesting idea. What do you think that would look like in the context of the Meta Environment? Maybe during provision, we call `wp eval-file import-sample-data.php`, and that...

Hmmm, `wme_import_database` does try to create them, with `mysql -u root --password=root -e "CREATE DATABASE IF NOT EXISTS $1;"`. I wonder why that's failing; did you get any error messages...

#27 might be related.

#41 might also be related

it doesn’t look like there’s anything in the code that creates those tables, were they just created manually on production?