Reaction Base - A base Docker image for Reaction Commerce

Build

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

FROM reactioncommerce/base:latest

Then you can build the image with:

reaction build reactioncommerce/reaction:latest
# or
docker build -t reactioncommerce/reaction:latest .

Run

Now you can run your container with the following command... (note that the app listens on port 3000 because it is run by a non-root user for security reasons and non-root users can't run processes on port 80)

docker run -d \
  -e ROOT_URL=http://example.com \
  -e MONGO_URL=mongodb://url \
  -e MAIL_URL=smtp://user:pass@mail.example.com:587 \
  -p 80:3000 \
  reactioncommerce/reaction:latest

Delay startup

If you need to force a delay in the startup of the Node process (for example, to wait for a database to be ready), you can set the STARTUP_DELAY environment variable to any number of seconds. For example, to delay starting the app by 10 seconds, you would do this:

docker run -d \
  -e ROOT_URL=http://example.com \
  -e MONGO_URL=mongodb://url \
  -e STARTUP_DELAY=10 \
  -p 80:3000 \
  reactioncommerce/reaction:latest

Build Options

This base image supports setting custom build options that let you modify what gets installed. You can use Docker build args to accomplish this. The currently supported options are to install PhantomJS, MongoDB, or any list of apt-get dependencies (this image is built on debian:jesse).

If you choose to install Mongo, you can use it by not supplying a MONGO_URL when you run your app container. The startup script will start Mongo inside the container and tell your app to use it. If you do supply a MONGO_URL, Mongo will not be started inside the container and the external database will be used instead. (Note that having Mongo in the same container as your app is just for convenience while testing/developing. In production, you should always use a separate Mongo deployment or at least a separate Mongo container).

When you build your image, you can set any of the following values:

docker build \
  --build-arg APT_GET_INSTALL="curl git wget" \
  --build-arg INSTALL_MONGO=true \
  --build-arg INSTALL_PHANTOMJS=true \
  --build-arg NODE_VERSION=4.8.4 \
  -t myorg/myapp:latest .

Development Builds

You can optionally avoid downloading Meteor every time when building regularly in development. Add the following to your Dockerfile instead...

FROM reactioncommerce/base:devbuild

However, this isn't recommended for your final production build because it creates a much larger image, but it's a time saver when you're building often in development. The first build you run will download/install Meteor and then every subsequent build will be able to skip that step and just build the app.

Docker Compose

Add a docker-compose.yml to the root of your project with the following content (edit the app image name to match your build name if needed).

# docker-compose.yml

reaction:
  image: reactioncommerce/reaction:latest
  ports:
    - 80:3000
  links:
    - mongo
  environment:
    - ROOT_URL=http://example.com
    - MONGO_URL=mongodb://mongo:27017/reaction

mongo:
  image: mongo:latest --storageEngine=wiredTiger

And then start the app and database containers with...

docker-compose up -d

License

MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

vtrbtf/base