We think Docker is one of the easiest ways to deploy modern apps and it's currently the recommended approach if you're hosting your own Reaction Commerce shop. If you aren't using a customized version of Reaction, there are only a few steps to get up and running and you don't even need to know much about Docker to do it. Let's get started!
First, you should find the Docker installer for your platform. This will install all of the Docker tools that you'll need for the rest of this section.
As described by Docker:
- Docker Engine provides the core functions you need to create Docker images and run Docker containers.
- Docker Compose defines and manages multi-container applications.
- Docker Machine automates Docker host provisioning on your network or in the cloud.
The following documentation only aims to show you how to setup a production deployment of Reaction Commerce. If you would like to learn more about the basics of Docker and how it might be useful for your development workflow, we strongly encourage reading Docker's Getting Started docs and going through some of their beginner tutorials.
Ok, let's do this!
Since the default Docker install only applies to a local development environment, the rest of these docs will assume you will be running Docker on a remote machine on the public internet so your containers will be accessible to anyone. Aside from the server setup, the process for running containers is identical either way, so you can go through the same steps locally to test your containers before deploying them publicly.
Docker Machine has drivers for most of the major cloud providers. They each have their own settings, but the process is essentially the same for all of them. We're going to focus on the Digital Ocean driver because it's one of the easiest to use. Only a few settings are required to start a new server, but see the Digital Ocean driver docs for all of the available options.
Before you start a machine, you'll need to get an API key from your Digital Ocean account. See "How Do I Get My API Credentials?"
Once you have that, you're ready to use Docker Machine to provision a server. To do so, run:
docker-machine create \ --driver digitalocean \ --digitalocean-access-token <your API key> \ --digitalocean-size 1gb \ reaction-host
That command is fairly self-explanatory. The name at the end (
reaction-host) can be anything you want. That's just a name for the machine that you will use to reference it with future commands.
Also note that the above command will create your server in the
nyc3 region by default. If you'd like to change this, you can use the
--digitalocean-region flag to set a different region. Or you can set the
DIGITALOCEAN_REGION environment variable to set a different default region to be used for all
Once your server is done launching, you just need to point Docker at it to start launching containers. You can do that with the following command:
eval "$(docker-machine env reaction-host)"
Now when you run Docker commands, they will be executing on the remote server instead of your local machine. Ok, let's fire up some Docker containers on your new server!
If you don't have a customized version of Reaction Commerce, you can use our official release builds that are available on Docker Hub as
reactioncommerce/reaction:latest. The official releases are built by Circle CI every time code is merged into the master branch on Github.
All you need to run the latest stable build of Reaction is a single Docker command (assuming you have a Mongo database hosted somewhere - e.g. Compose.io, etc.)
docker run -d \ -p 80:3000 \ -e ROOT_URL="http://<your app url>" \ -e MONGO_URL="mongodb://<your mongo url>" \ -e REACTION_EMAIL="firstname.lastname@example.org" \ -e REACTION_USER="admin-username" \ -e REACTION_AUTH="admin-password" \ reactioncommerce/reaction:latest
Let's break down what's going on here...
The first argument (
-d) means "detached" mode. This allows your terminal to disconnect from the running container while it continues to run in the background.
-p 80:3000. That means that traffic going to port 80 on your Docker host will route to port 3000 on the container (Reaction's default exposed port). So, in short...
-p host:container More info.
The next two lines (
MONGO_URL) are standard environment variables that are required by all deployed Meteor apps.
ROOT_URL should be set to the URL that users will reach your site with and
MONGO_URL should be the URL of your MongoDB deployment. (Note that you can and should use a
MONGO_OPLOG_URL if your Mongo deployment is a replica set. More info about the Mongo Oplog and Meteor).
And finally, the last 3 environment variables (
REACTION_AUTH) are for your default admin user in Reaction. If these variables are set the first time you run Reaction, a new user will be created for you with the email, username, and password you provide.
Now the only thing left to do is point your domain name for your site at the host you created with docker-machine. To get the IP address of the host, you can run:
docker-machine ip <machine name>
So if you created you machine with the exact command above, it would be:
docker-machine ip reaction-host
Once you have your host IP, go to your domain name provider and point your domain name at that IP.
That's it. You're done! Once your DNS records update, you should then be able to access your deployed Reaction Commerce shop.
Let's customize locally, and build your docker image.
First, you should already have a local reaction folder, if not, look at the installation docs.
After initializing with:
And running reaction with:
Then add your theming and customizations using the customization guide. Now you have a customized Reaction Commerce with all your shiny new npm packages and theming. It runs great locally and you have built a local custom image using:
docker build --build-arg TOOL_NODE_FLAGS="--max-old-space-size=2048" -t mycustom .
If you're having trouble at this step, configure the number passed into
max-old-space-size for your app's needs.
Which you can verify with:
docker images mycustom REPOSITORY TAG IMAGE ID CREATED SIZE mycustom latest d21371bbdba3 2 hours ago 359MB
Now to get your image online so your server can access it.
Publishing on Docker Hub
Log into your dockerhub account:
Tag your local image:
docker tag mycustom dockerhubuser/mycustom:mytag
Push it up to docker hub:
docker push dockerhubuser/mycustom:mytag
Pull it on a server:
docker pull dockerhubuser/mycustom:mytag
docker run -d \ -p 80:3000 \ -e ROOT_URL="http://<your app url>" \ -e MONGO_URL="mongodb://<your mongo url>" \ -e REACTION_EMAIL="email@example.com" \ -e REACTION_USER="admin-username" \ -e REACTION_AUTH="admin-password" \ mydockerhubuser/mycustom:mytag
Using Docker Compose
You can also use Docker Compose to run Reaction and Mongo in separate connected Docker containers.
We've included a demo docker-compose file in the repository. In its current basic form, it is meant for quickly running a demo of your production build. It can also serve as starting point for your production docker-compose setup.
If you have a custom Docker image of your Reaction app, you can modify the
docker-compose-demo.yml file to point to use it by changing the
image name of the
services: reaction: image: custom-image depends_on: - mongo ....
Then you start the app by runnung the
docker-compose up command and specifying your Compose file
docker-compose -f docker-compose-demo.yml up -d
This will pull down the specified Docker images (if not available locally). After pulling, the images are then started for you in the background. You can connect to the logs from your reaction instance with
docker-compose logs reaction --follow From the logs, you'll see when the app is up and you can then load it in a browser.