(feat): storefront using reaction docker base

[nnnnat]

Issue

Needed the Storefront example application to run within the Reaction Commerce Docker setup. Also needed a way for the Storefront container to communicate with the GraphQl service container.

Solution

Added all the necessary docker config files from the Reaction Base.
Created a network definition that both containers can communicate on.

Testing

Follow the setup steps within the README.
The Storefront app should start and run at localhost:4000 with no errors in the terminal.

Notes

You'll need to run the Storefront app with docker-compose up -d && docker-compose logs -f web to see any terminal logs.

[nnnnat]

@aldeed @ticean we were able to get this docker setup working but one issue we're having is the yarn install doesn't seem to install anything when running docker-compose up or docker-compose up --build. If we run yarn install locally before starting the container everything works fine. Not sure if I'm setting the build env correctly.

[aldeed]

Just a minor suggestion.

Regarding yarn install, it is a build-stage thing, so it should not be running on dc up but it should on dc up --build. If it doesn't, maybe try a full docker-compose down --rmi local followed by docker-compose build (and delete node_modules before doing that). Not sure if there is a difference.

After the initial build, it should work to dcrun yarn before dc up if there are any lockfile changes not yet installed.

It may help to make the same change I made in reaction docker-compose.yml, to add under service volumes:

- reaction-next-starterkit_node_modules:/usr/local/src/reaction-app/node_modules # do not link node_modules in, and persist it between dc up runs

And under the main volumes:

reaction-next-starterkit_node_modules

[aldeed]

I would destructure these (including METEOR_TOKEN) from process.env toward the top of the file and check each one throwing a specific error if it isn't set. That way when someone inevitably starts it up with improper configuration they'll get a more helpful error message like "You must set PROTOCOL env variable".

I'm also not sure why it would be necessary to break this up rather than just having a single GRAPHQL_URL variable.

[willopez]

LGTM, I was able to get the projects running with no errors. Good work!

[mikemurray]

👍 Works for me