Rocket.Chat

Deploy Rocket.Chat, the ultimate open source web chat platform, with Ansible!

Notes

• master has been rebased on v2.0 and is now the most current code of the role (Instead of it being the 1.9-compatible version.) If you want the latest code, just don't include any version at all and ansible-galaxy will pull in the latest tag, or you can include version: master to always be current with development.
• v1.9 users can continue to use tags v1.9 and v1.9.0, and an ansible_1.9 branch remains, though little if any backports will be made there.

Features

• Optional full stack deployment: Fully deploy Rocket.Chat, including MongoDB & an Nginx reverse SSL proxy. Or, deploy Rocket.Chat and integrate with your existing MongoDB and/or Nginx instances/deployment methods.

• Optional automatic SSL cert generation: Automatically generate SSL certs for HTTPS connectivity via an Nginx reverse proxy. Or, deploy your own SSL certs!

• Optional automatic upgrades [requires Ansible 2.0]: If a new version of Rocket.Chat is released, or if you want to follow development for testing purposes, simply update the rocket_chat_version to whichever release you wish to deploy (see the Rocket.Chat releases page, set rocket_chat_automatic_upgrades to true and let this role do the rest! If there's a change to the code deployed to your Rocket.Chat server (either because of a remote change to the rocket_chat_version you're following, 'latest' or 'develop' for instance, or because you set a new rocket_chat_version to fetch), this role will handle the upgrade and redeployment of the Rocket.Chat service, keeping your data in tact. Note: This functionality requires Ansible 2.0. See how to fetch the 2.0 version of this role in the Install from Ansible Galaxy section

Supported Platforms

Debian

• Strect (9)
• Buster (10)

Ubuntu

• Bionic Beaver: 18.04 LTS
• Xenial: 16.04 LTS
• Trusty: 14.04 LTS

EL (RHEL/CentOS)

• 7

If you'd like to see your distribution/operating system supported, please raise an issue!

Running into problems?

Please be sure you've read the FAQ and all documentation before raising an issue.

Role Variables

All variables have sane defaults set in defaults/main.yml

Defaults

Some variables differ between operating systems/distributions. These are set in the vars/ directory, typically in a file named after the distribution.

RHEL/CentOS variables

Set in vars/RedHat.yml

RHEL/CentOS 7 variables

Set in vars/RedHat_7.yml

Debian variables

Set in vars/Debian.yml

Debian 8 variables

Set in vars/Debian_8.yml

Ubuntu variables

Set in vars/Ubuntu.yml

Ubuntu 16 variables

Set in vars/Ubuntu_15.yml

Ubuntu 14 variables

Set in vars/Ubuntu_14.yml

Install this role from Ansible Galaxy

This role is available for download from Ansible Galaxy. To install this role, and track it in your Ansible code-base, use something similar to the following in your requirements.yml:

- src: RocketChat.Server
  version: v1.9.0
  path: roles/external/

Note: you must specify version as v1.9.0 if you're still using Ansible 1.9.4

Install the Ansible 2.0 version of this role

With the release of Ansible 2.0, this role is officially supported with some performance enhancements and extra features (automatic upgrades, for instance). To use the Ansible 2.0 version of this role, you can install it using the ansible-galaxy command line tool using a requirements.yml (both mentioned above) to specify the version you wish to use.

Here's an example requirements.yml file to install via ansible-galaxy will fetch the Ansible 2.0 code:

  - src: RocketChat.Server
    path: roles/external

Note: master has been rebased on v2.0 and is now the most current code of the role. If you want the latest just don't include any version at all and ansible-galaxy will pull in the latest tag, or you can include version: master to always be current.

Example Playbook

A simple playbook to run this role on all chat_servers systems:

  - hosts: chat_servers
    roles:
     - RocketChat.Server

A playbook to deploy Rocket.Chat to chat_servers but exclude the deployment of MongoDB and use an external instance. Also permit automatic upgrades of Rocket.Chat (Ansible 2.0 required for rocket_chat_automatic_upgrades! See the Install from Ansible Galaxy secion):

  - hosts: chat_servers

    vars:
      rocket_chat_automatic_upgrades: true
      rocket_chat_include_mongodb: false
      rocket_chat_mongodb_server: 10.19.3.24

    roles:
      - RocketChat.Server

FAQ

• When I try to deploy using this role, it fails on the Fetch the Rocket.Chat binary tarball task If deployment fails with a message similar to the following, this is because the role hasn't been updated to reflect the SHA256 hash sum of the latest Rocket.Chat release tarball

  TASK [RocketChat.Server : Fetch the Rocket.Chat binary tarball] ****************
  fatal: [chat1]: FAILED! => {"changed": false, "failed": true, "msg": "The checksum for /var/lib/rocket.chat/rocket.chat-latest.tgz did not match e6caca890c86f79595da14398dd3ab0c0d3222932d6a8a1b38c6e5082531acd2; it was 21ef5ee220671e5f514f240d1423514c5780d81d6ffba8720d19660079099925."}

  Right now, maintenance of this variable is a manual process. In the meantime you can simply set this variable's value yourself; via host_vars, group_vars, vars in your playbook, or with -e when running ansible-playbook, etc.

Available tags

To run a specific set of plays, with the --tags flag, the available tags are:

• vars
• build
• mongodb
• repo
• nginx
• upgrade
• service

Management of the Rocket.Chat service

This role will deploy a service named rocketchat. You can use your native service management system to start/stop/reload/restart the service.

Testing via Vagrant

To test this role, you'll find a Vagrantfile and provision.yml playbook in the tests/ directory. This is, as you might have guessed, for running test deployments via Vagrant.

If you'd like to test some changes, or simply see how the role works/provision a little play Rocket.Chat server locally, you can cd into tests/ and run vagrant up (provided you have Vagrant & VirtualBox installed).

If you take a look at the Vagrantfile, you'll see there's a deployment for each currently supported platform - simply comment out any you don't want to deploy (don't forget their Ansible config at the bottom, either!). Once deployment is finished, if you want to try Rocket.Chat out, you can visit http://localhost:4000 in your browser (the port 4000 varies here, based on which platform you're deploying, see the forwarded_port value for your platform).

TODO

• [ ] Use Let's Encrypt for SSL

License

MIT

Issues/Contributions

Feel free to: Raise an issue Contribute