build: update Docker dev environment

[eatyourgreens]

• add some more local code directories to the docker dev build.
• update the docs.

[eatyourgreens]

I think I've got all the places that you might want to make changes while working on the app, but I could be wrong.

[martinjrobins]

there are a few more (lib, scripts, config, docs, ...). Perhaps you could map the entire root dir to /app/?

[eatyourgreens]

I'm not sure about directories like docs, because they aren't used by the running Next.js app.

It might be worth adding a docs service to the compose file, though, so you could see the Next.js app on one port, and the docs site on another.

I'm also wondering whether to add a CLI shell so that people can run yarn scripts inside a container. At the moment, you can't easily run the tests in Docker.

[eatyourgreens]

Just tried running the tests in a container, and they failed with missing dependency errors. That's a problem for another day.

docker compose -f docker-compose.dev.yml run --rm gutenberg yarn e2e

[martinjrobins]

lib would be an important directory to include

[martinjrobins]

there are a few more (lib, scripts, config, docs, ...). Perhaps you could map the entire root dir to /app/?

[eatyourgreens]

I can build and run this locally, from a clean install of the Gutenburg repo. When I make changes in VS Code, I see them reflected in the dev site on http://localhost:3000. I think this will work to get the ICR team up and running with Gutenberg on Windows at tomorrow's hackathon.