Skip to content

Commit ed42266

Browse files
LuluGOgeekgonecrazy
authored andcommitted
adding more info to Digital Ocean doc page (RocketChat#1470)
* adding more info to Digital Ocean doc page * possible changes to motd * changes to motd * fix trailing whitespace
1 parent e3482db commit ed42266

File tree

1 file changed

+64
-0
lines changed
  • installation/paas-deployments/digital-ocean

1 file changed

+64
-0
lines changed

installation/paas-deployments/digital-ocean/README.md

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,3 +4,67 @@ You can now install Rocket.Chat on DigitalOcean using a 1-Click install from the
44

55
[![do-btn-blue](https://user-images.githubusercontent.com/51996/58146107-50512580-7c1a-11e9-8ec9-e032ba387c2a.png)](https://marketplace.digitalocean.com/apps/rocket-chat?action=deploy&refcode=1940fe28bd31)
66

7+
---
8+
9+
After you create your 1-Click install using the Rocket.Chat app in DigitalOcean Marketplace, you'll likely want a registered domain name to access Rocket.Chat.
10+
11+
We recommend setting up an A record from your domain to your servers IP address. Ex: chat.mycompany.com
12+
13+
Rocket.Chat will not work with HTTPS out of the box because certificates are unique for each instalation, but with this setup HTTPS will be available using Let's Encrypt certificates.
14+
15+
After the Rocket.Chat One-Click is finished and your domain is setup. You will need to login to your droplet to finish setup.
16+
17+
```
18+
ssh root@your_droplet_ip
19+
```
20+
21+
Once you are connected you should see something like:
22+
23+
```
24+
Rocket.Chat is the leading open source team chat software solution. Free, unlimited and completely customizable with on-premises and SaaS cloud hosting.
25+
Replace email, HipChat & Slack with the ultimate team chat software solution.
26+
27+
Out of the box you can access Rocket.Chat server at: http://Droplet-IP:3000
28+
29+
You will likely want a registered domain name to access Rocket.Chat. If you would like your server to be accessible over https we provide the option to use letsencrypt by running:
30+
# rocketchatctl configure --lets-encrypt --root-url=https://chat.yourcompany.com --letsencrypt-email=admin@yourcompany.com
31+
32+
In case you do not own a registered domain, you could use the public IP of your droplet, but traefik will not be able to fetch certificates for you so you will see a privacy alert message when loading https://droplet-IP
33+
# rocketchatctl configure --lets-encrypt --root-url=https://droplet-IP --letsencrypt-email=admin@yourcompany.com
34+
35+
If you would like https with something other than letsencrypt provided certificates you will have to manually edit the traefik config to add it.
36+
37+
In case you do own a registered domain, but you do not want to use traefik, you can just configure your site URL running:
38+
# rocketchatctl configure --rocketchat --root-url=http://chat.yourcompany.com:3000
39+
40+
Keep your RocketChat server updated using rocketchatctl update. Run rocketchatctl -h to see the full list of available options.
41+
42+
Looking for how to use Rocket.Chat? Be sure to check our docs: https://rocket.chat/docs
43+
44+
Checkout our Digital Ocean docs: https://rocket.chat/docs/installation/paas-deployments/digital-ocean/
45+
46+
Need some help? Join our community forums https://forums.rocket.chat
47+
```
48+
49+
Besides the recommended setup you can out of the box access Rocket.Chat server at: [http://Droplet-IP:3000](<http://Droplet-IP:3000>)
50+
51+
## Setting up HTTPS
52+
53+
We recommend you to finish the Traefik loadbalancer configuration to handle HTTPS. Run this command to fetch Let's Encrypt certificates for your installation:
54+
55+
```
56+
rocketchatctl configure --lets-encrypt --root-url=https://chat.yourcompany.com --letsencrypt-email=admin@yourcompany.com
57+
```
58+
59+
You can then access at: [https://chat.yourcompany.com](<https://chat.yourcompany.com>) replacing chat.yourcompany.com with the address you set in your DNS.
60+
61+
The Loadbalancer will redirect HTTP to HTTPS
62+
63+
## Firewall
64+
65+
This image comes with a ufw firewall enabled and the ports allowed for incomingo traffic are:
66+
67+
- ssh 22
68+
- http 80
69+
- https 443
70+
- rocketchat 3000

0 commit comments

Comments
 (0)