Instead of using the standard Docker commands, you may wish for a bit more automated management of the deployment. This is where the use of Docker-compose may come in handy.
- Make sure you have Docker and Docker-compose installed and operational.
docker-compose.ymlbased on our example. This is the ONLY file you will need. You can create this file on your own machine by copy and pasting the content.
image: rocketchat/rocket.chat:developto specify which image you wish to use (see section Docker Images Available )
ROOT_URLto match your domain name or IP address
You can download our docker-compose.yaml:
curl -L https://raw.githubusercontent.com/RocketChat/Rocket.Chat/develop/docker-compose.yml -o docker-compose.yml
Start the mongodb server by:
docker-compose up -d mongo
The first time you start mongo, you’ll also need to initialize it before being able to use Rocket.Chat. Ensure that mongo is in the running state, then:
docker-compose up -d mongo-init-replica
Mongo supports 24 x 7 operations and live backup. You should not need to restart it too frequently. See mongodb documentations for proper operation and management of a mongo server.
Once you’re sure that mongodb is up and running:
docker-compose up -d rocketchat
Optionally, if you want to manage your messages and configuration information, edit the file again to uncomment the volume mounts. Make sure you have a
data subdirectory to mount and store the data.
Optionally, if you want a bot, so you don’t have to talk to yourself, after you’ve created an admin user and also a bot user, edit the file
docker-compose.yml again to change the variables
ROCKETCHAT_PASSWORD in the hubot section and then start up hubot:
docker-compose up -d hubot
To update the
rocketchat docker image to the latest version, you can use the following commands. Your data should not be affected by this, since it’s located in the
docker pull rocketchat/rocket.chat:develop docker-compose stop rocketchat docker-compose rm rocketchat docker-compose up -d rocketchat