Unverified Commit d06bddd5 authored by Sean Packham's avatar Sean Packham Committed by GitHub
Browse files

Merge pull request #465 from RocketChat/fix-markdown-installation

Fix Markdown Lint issues on Installation Folder
parents 3979e5a7 8f39245a
# Rocket.Chat Cloud
### You can request for a beta hosting of Rocket.Chat hosting service!
## You can request for a beta hosting of Rocket.Chat hosting service
You will have a server up and running, professionally managed, without installations, configuration, maintenance and management head-aches. Just go to https://rocket.chat/hosting and get your team up and running in seconds.
You will have a server up and running, professionally managed, without installations, configuration, maintenance and management head-aches. Just go to <https://rocket.chat/hosting> and get your team up and running in seconds.
Canadian Educators, please email to cloud@rocket.chat and request for _"Canadian Hosting beta"_ with some information about your class size and intented uses.
......
......@@ -6,7 +6,7 @@ This guide covers the following:
2. Hosting a domain name with Amazon Route 53
3. Securing your server with a free SSL certificate from Let's Encrypt
### Table of Contents
## Table of Contents
1. [Launch an EC2 Instance](#1-launch-an-ec2-instance)
2. [Allocate an Elastic IP](#2-allocate-an-elastic-ip)
......@@ -19,144 +19,160 @@ This guide covers the following:
9. [Reboot & Test](#9-reboot--test)
10. [Use it!](#10-use-it)
### 1. Launch an EC2 instance.
### 1. Launch an EC2 instance
#### In AWS Services, go to **EC2**, **Instances**, and **Launch Instance**
1. Choose an AMI
* Select **Ubuntu Server 14.04 LTS** AMI
2. Choose an Instance Type
* Select Type: **t2.micro** and click **Next**
3. Configure Instance Details
* Leave as defaults or change if needed and click **Next**
4. Add Storage
* Adjust the size, or add a second encrypted volume if needed and click **Next**
5. Tag Instance
* Add a Value to the **Name** Key and click **Next**
6. Configure Security group
* Create a new Security group if you would like to restrict traffic to a certain IP address range. **Note: If you will be using letsencrypt in Step 4 to get an SSL certificate, you will need to allow traffic to the server on port 80 until your certificate is created. After this, you may remove that security group and restrict access to a specific IP range.**
7. Review Instance Launch
* Click **Launch**
8. Key Pairs
* Choose an existing key pair or create a new one and **Launch Instance**
1. Choose an AMI
- Select **Ubuntu Server 14.04 LTS** AMI
2. Choose an Instance Type
- Select Type: **t2.micro** and click **Next**
3. Configure Instance Details
- Leave as defaults or change if needed and click **Next**
4. Add Storage
- Adjust the size, or add a second encrypted volume if needed and click **Next**
5. Tag Instance
- Add a Value to the **Name** Key and click **Next**
6. Configure Security group
- Create a new Security group if you would like to restrict traffic to a certain IP address range. **Note: If you will be using letsencrypt in Step 4 to get an SSL certificate, you will need to allow traffic to the server on port 80 until your certificate is created. After this, you may remove that security group and restrict access to a specific IP range.**
7. Review Instance Launch
- Click **Launch**
8. Key Pairs
- Choose an existing key pair or create a new one and **Launch Instance**
### 2. Allocate an Elastic IP
#### In AWS Services, go to **EC2** and **Elastic IPs**
1. Select **Allocate New Address**
2. Search for your instance, and click **Associate**
3. In the details below, copy the **Public DNS** value. You will need it in the DNS step. (It should be in this format: ec2-11-222-33-44.us-west-2.compute.amazonaws.com)
1. Select **Allocate New Address**
2. Search for your instance, and click **Associate**
3. In the details below, copy the **Public DNS** value. You will need it in the DNS step. (It should be in this format: ec2-11-222-33-44.us-west-2.compute.amazonaws.com)
### 3. Configure DNS w/ AWS Route 53
#### In AWS Services, go to **Route 53**
* **Create Hosted Zone**
* Enter Domain Name and select Type: **Public Hosted Zone**, then **Create**
* Select your new Hosted Zone and **Create Record Set**
* Enter the subdomain (if desired), select Type **CNAME**, enter the Public DNS name from the above step to the value field and click **Create**
- **Create Hosted Zone**
- Enter Domain Name and select Type: **Public Hosted Zone**, then **Create**
- Select your new Hosted Zone and **Create Record Set**
- Enter the subdomain (if desired), select Type **CNAME**, enter the Public DNS name from the above step to the value field and click **Create**
### 4. Get an SSL certificate from Let's Encrypt
#### We will use **letsencrypt** to get a free & open-source SSL certificate
1. SSH to your instance
`ssh -i <path_to_key_file.pem> ubuntu@<public_ip_address>`
Note: You may replace <public_ip_address> with domain name if your DNS has resolved.
1. SSH to your instance:
`ssh -i <path_to_key_file.pem> ubuntu@<public_ip_address>`
Note: You may replace <public_ip_address> with domain name if your DNS has resolved.
2. Clone the **letsencrypt** repository from github. (If it is available via a package manager, you may use that).
`sudo git clone https://github.com/letsencrypt/letsencrypt /opt/letsencrypt`
This will copy the **letsencypt** repository to `/opt/letsencrypt`
`sudo git clone https://github.com/letsencrypt/letsencrypt /opt/letsencrypt`
This will copy the **letsencypt** repository to `/opt/letsencrypt`
3. Confirm no applications are listening to port 80:
`netstat -na | grep ':80.*LISTEN'`
If any processes are returned, kill them.
`netstat -na | grep ':80.*LISTEN'`
If any processes are returned, kill them.
4. Get Certificate from Let's Encrypt
Change to Let's Encrypt repository location
`cd /opt/letsencrypt`
Run the Standalone plugin. (This will open a web server listening on port 80 to validate the server).
Change to Let's Encrypt repository location
`cd /opt/letsencrypt`
Run the Standalone plugin. (This will open a web server listening on port 80 to validate the server).
```
./letsencrypt-auto certonly --standalone --email <emailaddress@email.com> -d <domain.com> -d <subdomain.domain.com>
```
Note: Second (or more) domain is optional.
5. If you would like to restrict traffic to your instance on AWS, you may now restrict the security groups. Make sure you allow **TCP/22** from your current location for the SSH connection, as well as **TCP/443** from the location you wish to use to access from.
6. Check for certificates and keys
The following files will be created in `/etc/letsencrypt/archive` with symbolic links placed in `/etc/letsencrypt/live/<domain.com>`
* **cert.pem** - domain certificate
* **chain.pem** - Let's Encrypt chain certificate
* **fullchain.pem** - both the above certs (This will be your **certificate file**)
* **privkey.pem** - certificate's private key (This will be your **certificate key file**).
The following files will be created in `/etc/letsencrypt/archive` with symbolic links placed in `/etc/letsencrypt/live/<domain.com>`
- **cert.pem** - domain certificate
- **chain.pem** - Let's Encrypt chain certificate
- **fullchain.pem** - both the above certs (This will be your **certificate file**)
- **privkey.pem** - certificate's private key (This will be your **certificate key file**).
Confirm by listing the following directory
`sudo ls /etc/letsencrypt/live/<domain.com>`
### 5. Configure Nginx web server with TLS/SSL
1. Install Nginx web server.
`sudo apt-get install nginx`
`sudo apt-get install nginx`
2. Edit the Nginx configuration file.
* Backup the default config file for reference:
`cd /etc/nginx/sites-available`
`sudo mv default default.reference`
* Create a new file with the following contents. Replace <ABC.DOMAIN.COM> with your domain (it appears 4 times below). Make sure to update it in the path to your key files as well.
- Backup the default config file for reference:
`cd /etc/nginx/sites-available`
`sudo mv default default.reference`
- Create a new file with the following contents. Replace <ABC.DOMAIN.COM> with your domain (it appears 4 times below). Make sure to update it in the path to your key files as well.
`sudo nano /etc/nginx/sites-available/default`
```
server {
listen 443 ssl;
server_name <ABC.DOMAIN.COM>;
ssl_certificate /etc/letsencrypt/live/<ABC.DOMAIN.COM>/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/<ABC.DOMAIN.COM>/privkey.pem;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
root /usr/share/nginx/html;
index index.html index.htm;
# Make site accessible from http://localhost/
server_name localhost;
location / {
proxy_pass http://localhost:3000/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forward-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forward-Proto http;
proxy_set_header X-Nginx-Proxy true;
proxy_redirect off;
}
}
server {
listen 80;
server_name <domain.com>;
return 301 https://$host$request_uri;
}
```
* Explanation: remove the listen to port 80 by default and replace with port 443 ssl as well as giving the path to the certificate. Restrict to certain SSL protocols and ciphers (you may add more if you like). In the location section, use Nginx as a proxy to forward to port 3000 (where Rocket.Chat is set up. Create a second server block listening on port 80 that will redirect to https."
* Write & exit
* Stop Nginx:
```bash
server {
listen 443 ssl;
server_name <ABC.DOMAIN.COM>;
ssl_certificate /etc/letsencrypt/live/<ABC.DOMAIN.COM>/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/<ABC.DOMAIN.COM>/privkey.pem;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;
ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
root /usr/share/nginx/html;
index index.html index.htm;
# Make site accessible from http://localhost/
server_name localhost;
location / {
proxy_pass http://localhost:3000/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forward-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forward-Proto http;
proxy_set_header X-Nginx-Proxy true;
proxy_redirect off;
}
}
server {
listen 80;
server_name <domain.com>;
return 301 https://$host$request_uri;
}
```
- Explanation: remove the listen to port 80 by default and replace with port 443 ssl as well as giving the path to the certificate. Restrict to certain SSL protocols and ciphers (you may add more if you like). In the location section, use Nginx as a proxy to forward to port 3000 (where Rocket.Chat is set up. Create a second server block listening on port 80 that will redirect to https."
- Write & exit
- Stop Nginx:
`sudo service nginx stop`
* Test starting Nginx to make sure there are no syntax errors in your configuration file. If there are errors in your file, it will give you a clue as to the issue.
- Test starting Nginx to make sure there are no syntax errors in your configuration file. If there are errors in your file, it will give you a clue as to the issue.
`sudo nginx -t`
* If the syntax test is successful, Start Nginx:
- If the syntax test is successful, Start Nginx:
`sudo service nginx start`
* Confirm that it is running properly by opening a web browser and going to your domain name. You will get a page stating **502 Bad Gateway** This is expected. Look above, next to the domain name, you should see a lock icon. If you click this, you should be able to see the certificates, where your browser will verify that Let's Encrypt Authority X1 issued this website's certificate, as well as a report of which cipher is being used.
* Note: The certificate will expire in 90 days
* ** TODO: Add script for auto-renewal of certificate.
- Confirm that it is running properly by opening a web browser and going to your domain name. You will get a page stating **502 Bad Gateway** This is expected. Look above, next to the domain name, you should see a lock icon. If you click this, you should be able to see the certificates, where your browser will verify that Let's Encrypt Authority X1 issued this website's certificate, as well as a report of which cipher is being used.
- Note: The certificate will expire in 90 days
- ** TODO: Add script for auto-renewal of certificate.
### 6. Install Docker & Docker Compose
1. SSH to your instance
`ssh -i <path_to_key_file.pem> ubuntu@<public_ip_address>`
Note: You may replace <public_ip_address> with domain name if your DNS has resolved.
`ssh -i <path_to_key_file.pem> ubuntu@<public_ip_address>`
Note: You may replace <public_ip_address> with domain name if your DNS has resolved.
2. Install Docker (and any dependencies)
`sudo wget -qO- https://get.docker.com/ | sh`
`sudo wget -qO- https://get.docker.com/ | sh`
3. Add ubuntu user to docker group to use Docker as a non-root user.
`sudo usermod -aG docker ubuntu`
`sudo usermod -aG docker ubuntu`
4. Install Docker Compose:
`sudo -i`
`curl -L https://github.com/docker/compose/releases/download/1.4.2/docker-compose-Linux-x86_64 > /usr/local/bin/docker-compose`
`chmod +x /usr/local/bin/docker-compose`
`exit`
`sudo -i`
`curl -L https://github.com/docker/compose/releases/download/1.4.2/docker-compose-Linux-x86_64 > /usr/local/bin/docker-compose`
`chmod +x /usr/local/bin/docker-compose`
`exit`
5. Logout, and log back in again.
`exit`
`exit`
6. SSH to your instance again following the directions above
### 7. Set up Docker Containers
1. Create local directories
`sudo mkdir -p /var/www/rocket.chat/data/runtime/db`
`sudo mkdir -p /var/www/rocket.chat/data/dump`
`sudo mkdir -p /var/www/rocket.chat/data/runtime/db`
`sudo mkdir -p /var/www/rocket.chat/data/dump`
2. Create docker-compose.yml, **replacing the ROOT_URL of ABC.DOMAIN.COM with your site**
`sudo nano /var/www/rocket.chat/docker-compose.yml`
`sudo nano /var/www/rocket.chat/docker-compose.yml`
```
db:
image: mongo:3.0
......@@ -175,67 +191,76 @@ This guide covers the following:
ports:
- 3000:3000
```
* Write & Exit
- Write & Exit
### 8. Automatic start & restarting with Upstart
1. Create upstart job for MongoDB
`sudo nano /etc/init/rocketchat_mongo.conf`
```
description "MongoDB service manager for Rocket.Chat"
# Start MongoDB after docker is running
start on (started docker)
stop on runlevel [!2345]
# Automatically Respawn with finite limits
respawn
respawn limit 99 5
# Path to our app
chdir /var/www/rocket.chat
script
# Showtime
exec /usr/local/bin/docker-compose up db
end script
```
`sudo nano /etc/init/rocketchat_mongo.conf`
```bash
description "MongoDB service manager for Rocket.Chat"
# Start MongoDB after docker is running
start on (started docker)
stop on runlevel [!2345]
# Automatically Respawn with finite limits
respawn
respawn limit 99 5
# Path to our app
chdir /var/www/rocket.chat
script
# Showtime
exec /usr/local/bin/docker-compose up db
end script
```
2. Save and Exit.
3. Create the upstart job for Rocket.Chat
`sudo nano /etc/init/rocketchat_app.conf`
```
description "Rocket.Chat service manager"
# Start Rocket.Chat only after mongo job is running
start on (started rocketchat_mongo)
stop on runlevel [!2345]
`sudo nano /etc/init/rocketchat_app.conf`
```
description "Rocket.Chat service manager"
# Start Rocket.Chat only after mongo job is running
start on (started rocketchat_mongo)
stop on runlevel [!2345]
# Automatically Respawn with finite limits
respawn
respawn limit 99 5
# Automatically Respawn with finite limits
respawn
respawn limit 99 5
# Path to our app
chdir /var/www/rocket.chat
# Path to our app
chdir /var/www/rocket.chat
script
# Bring up Rocket.Chat app
exec /usr/local/bin/docker-compose up rocketchat
end script
```
script
# Bring up Rocket.Chat app
exec /usr/local/bin/docker-compose up rocketchat
end script
```
### 9. Reboot & Test
1. Restart
`sudo reboot`
`sudo reboot`
2. Wait a minute or so and login with SSH again
`ssh -i <path_to_key_file.pem> ubuntu@<public_ip_address>`
`ssh -i <path_to_key_file.pem> ubuntu@<public_ip_address>`
3. Check status of docker
`sudo docker ps -a`
* When it's up and running, you should see 2 images, one for rocket.chat and one for mongo.
* If you don't see the containers yet, don't panic. It may take a few minutes to download and setup the containers. If you still don't see the images listed with the above `docker` command, check the logs of your upstart jobs.
sudo docker ps -a`
- When it's up and running, you should see 2 images, one for rocket.chat and one for mongo.
- If you don't see the containers yet, don't panic. It may take a few minutes to download and setup the containers. If you still don't see the images listed with the above `docker` command, check the logs of your upstart jobs.
`sudo cat /var/log/upstart/rocketchat_mongo.log`
`sudo cat /var/log/upstart/rocketchat_app.log`
* While the services are starting and downloading, the end of the logs (particularly rocketchat_app.log) will likely show the status of Download/Extract/Pull. If there are other errors, you will likely see this information in the log.
- While the services are starting and downloading, the end of the logs (particularly rocketchat_app.log) will likely show the status of Download/Extract/Pull. If there are other errors, you will likely see this information in the log.
### 10. Use it
### 10. Use it!
1. Login to your site at https://ABC.DOMAIN.COM
* Note: the first user to login will be an administrator
1. Login to your site at <https://ABC.DOMAIN.COM>
- Note: the first user to login will be an administrator
2. You can then use the native apps to connect to your Rocket.Chat server.
......@@ -4,15 +4,15 @@ You can install Rocket.Chat to Ubuntu VPS on Aliyun.
The recommended VPS configuration is:
* 2 GB RAM
* 10 GB disk
* 2 or 4 cores
- 2 GB RAM
- 10 GB disk
- 2 or 4 cores
However, lower performance configuration has been tested on a VPS with:
* 1 GB RAM
* 10 GB disk
* 1 core
- 1 GB RAM
- 10 GB disk
- 1 core
Follow these steps to install Rocket.Chat.
......@@ -50,7 +50,6 @@ docker ps
![aliyun docker verify](https://raw.githubusercontent.com/Sing-Li/bbug/master/images/aliyun2.png)
## Install docker-compose
Install docker-compose, follow the [latest release instructions](https://github.com/docker/compose/releases)
......@@ -60,6 +59,7 @@ For release 1.5.0, you can use:
```
curl -L https://github.com/docker/compose/releases/download/1.5.0/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
```
*(if or when this is blocked, you'll have to obtain Linux-x86_64 docker-compose binary via other means)*
Next, allow execution of docker-compose:
......@@ -88,6 +88,7 @@ Make two more directories for the mongodb database:
mkdir data
mkdir dump
```
## Create customized docker-compose.yml
Create a `docker-compose.yml` file with the following content:
......@@ -109,6 +110,7 @@ web:
ports:
- 8818:3000
```
Make sure you customize the file with `your-ip-address` in the `MONGO_URL` env variable.
## Pull the required docker images
......@@ -151,5 +153,3 @@ Your Rocket.Chat server can now be accessed over the Internet via:
```
http://your-ip-address:8818/
```
......@@ -5,4 +5,3 @@ Install Rocket.Chat on [Cloudron](https://cloudron.io) Smartserver:
[![Install](https://cloudron.io/img/button.svg)](https://cloudron.io/button.html?app=chat.rocket.cloudronapp)
The source code for the Cloudron Rocket.Chat can be found [here](https://git.cloudron.io/cloudron/rocketchat-app).
# Deploying Rocket.Chat on Galaxy
Prerequisites:
- Git
- Meteor
### Get Rocket.Chat code
## Get Rocket.Chat code
Download the source code first to be able to deploy to Galaxy
......
......@@ -5,10 +5,10 @@
2. SSH to the instance
3. run the following to install docker:
`sudo wget -qO- https://get.docker.com/ | sh`
`sudo wget -qO- https://get.docker.com/ | sh`
4. install a docker image for mongo db
`sudo docker run --name db -d mongo --smallfiles`
`sudo docker run --name db -d mongo --smallfiles`
5. install a docker image for rocketchat and connect it to mongodb. `ROOT_URL` should be substituted for your own domain:
......@@ -18,11 +18,11 @@
If you want the containers to start each time the instance reboots configure the following to the instance.
* click on the instance in the and hit "edit"
* Under "Custom metadata" add an item with
- click on the instance in the and hit "edit"
- Under "Custom metadata" add an item with
```
key: "startup-script"
value "sudo docker start db;
sudo docker start rocketchat"
```
......@@ -2,8 +2,8 @@
Two ways to deploy Rocket.Chat to Heroku:
* easy one click
* customized command line
- easy one click
- customized command line
## One Click automatic deploy
......@@ -43,8 +43,8 @@ This is the option that gives you full control. It is the preferred option for
First make sure you have the following installed:
* git
* Heroku CLI
- git
- Heroku CLI
Next, checkout the latest version of Rocket.Chat:
......@@ -88,21 +88,26 @@ git push heroku master
Rocket.Chat should now be running.
### Got Problems?
* Set the repository as the buildpack URL:
### Got Problems
- Set the repository as the buildpack URL:
```
heroku buildpacks:set https://github.com/AdmitHub/meteor-buildpack-horse.git
```
* Then try again
- Then try again
```
git push heroku master
```
* Still got problems, please raise an issue.
- Still got problems, please raise an issue.
### Caveats
* To add any service to an app, even if it is free, you will need to register a valid credit card with Heroku. Rocket.Chat needs both mongolab and logenteries services.
* Heroku (actually CloudFoundry) uses custom buildpacks to stage applications. The buildpack used by Rocket.Chat can take a very long time to build - since it needs to download Meteor and build the server image every time.
* You *must* set the ROOT_URL environment variable, as shown above, otherwise the server side will crash.
* Note mongolab's free sandbox plan does not support oplog tailing - check other plans if you need oplog.
* If you are scaling to multi-dynos on Heroku, and you have clients/customers still using older browsers that do not support WebSocket, you need to be mindful of sticky session support (BETA) on Heroku - see [sticky sessions on Heroku](https://devcenter.heroku.com/articles/session-affinity).
- To add any service to an app, even if it is free, you will need to register a valid credit card with Heroku. Rocket.Chat needs both mongolab and logenteries services.
- Heroku (actually CloudFoundry) uses custom buildpacks to stage applications. The buildpack used by Rocket.Chat can take a very long time to build - since it needs to download Meteor and build the server image every time.
- You *must* set the ROOT_URL environment variable, as shown above, otherwise the server side will crash.
- Note mongolab's free sandbox plan does not support oplog tailing - check other plans if you need oplog.
- If you are scaling to multi-dynos on Heroku, and you have clients/customers still using older browsers that do not support WebSocket, you need to be mindful of sticky session support (BETA) on Heroku - see [sticky sessions on Heroku](https://devcenter.heroku.com/articles/session-affinity).
# Hyper.sh
Rocket.Chat is a web chat application for communities and companies wanting to privately host their own chat service or for developers looking to build and evolve their own chat platforms. In this guide, we will demonstrate how to deploy a Rocket.chat container connected with a MongoDB container in seconds.
### 1. Register for your free Hyper credits
## 1. Register for your free Hyper credits
First take 2 minutes to sign up for Hyper, receive your free credits and install the CLI: [https://docs.hyper.sh/GettingStarted/index.html](https://docs.hyper.sh/GettingStarted/index.html)
### 2. Create a floating IP address
## 2. Create a floating IP address
``` bash
$ hyper allocate 1
xxx.xxx.xxx.xxx <-- Your floating IP
```
### 3. Clone the compose file
```
## 3. Clone the compose file
```
$ git clone https://github.com/hyperhq/Hyper_Rocket.Chat.git
Cloning into 'Hyper_Rocket.Chat'...
remote: Counting objects: 11, done.
......@@ -21,7 +24,8 @@ remote: Total 11 (delta 2), reused 10 (delta 1), pack-reused 0
Unpacking objects: 100% (11/11), done.
Marks-MacBook:workspace markcoleman$ cd Hyper_Rocket.Chat/
```
### 4. Add your FIP to the compose file
## 4. Add your FIP to the compose file
```
$ cat rocketchat_mongodb
......@@ -43,17 +47,17 @@ services:
restart: always
```
### 5. Start Rocket.Chat
## 5. Start Rocket.Chat
```
$ hyper compose up -f rocketchat_mongodb
Project [hyperrocketchat]: Starting project
[0/2] [db]: Starting
[1/2] [db]: Started
[1/2] [rocket.chat]: Starting
$ hyper compose up -f rocketchat_mongodb
Project [hyperrocketchat]: Starting project
[0/2] [db]: Starting
[1/2] [db]: Started
[1/2] [rocket.chat]: Starting
...
```
### Done!