With the release of Meteor 1.7, we changed the versioning of this repo and it's Docker builds to align with Meteor's release. Henceforth, releases in this repo will be tied to the corresponding Meteor release.

Sample version builds:

See Docker Hub for full list.

We do not commit to creating a new release of this repo with every Meteor version release. We intend to support versions used by Reaction. Pull requests are welcome for versions not included.

• Create a directory for the new version (following the existing name convention)
• Update the new Dockerfile as needed.
• Set the TAGS ENV in the options file to your release TAG
• Set the Meteor version ENV in the options file
• If this new version is the highest tag, search for and remove latest from the current options file it's located, and add it to the new options file
• Add any extra test step(s) needed in the test-script.sh
• Update History.md with the new release
• Open a PR to master with the changes.

Add the following to a Dockerfile in the root of your Reaction Commerce project:

FROM reactioncommerce/base:v1.7.0.1-meteor

Then you can build the image with this command (after setting your version):

VERSION=
docker build \
  --build-arg TOOL_NODE_FLAGS="--max-old-space-size=4096" \
  -t reactioncommerce/reaction:${VERSION} .

Note: Depending on the type of OS running the build, --max-old-space-size may require a different value (e.g 2048). See explanation of the Meteor issue here.

See Reaction's sample Dockerfile using the base image here.

Use docker-compose to run the app. A demo docker-compose file is included in the Reaction repo.

Run this command to start the app:

docker-compose -f docker-compose-demo.yml up

MIT License