Discourse/Noisebridge/2019-07-22 Rocketchat setup needs your help

From Noisebridge
Jump to navigation Jump to search

📜 Discourse Archive
This page is preserved verbatim from discuss.noisebridge.info, the Noisebridge community forum that operated roughly 2018–2022. The original site is defunct; this content was recovered via the Wayback Machine and is archived here as a primary source for Noisebridge history.
⮡ Original URL: https://discuss.noisebridge.info/t/rocket-chat-setup-needs-your-help/1171
📦 Verify on Wayback Machine
📅 Archived: 2020-11-07
🏷 Original category: Noisebridge

Rocket.chat setup needs your help[edit | edit source]


James

The latest build is running, but cannot be accessed by either IP or Nginx proxied URL at chat.noisebridge.info

If anyone wants to take a stab on it via Unicorn, please do. I cannot figure it out. Perhaps it is an easy fix. Good luck!

Here is the Nginx configuration

Docker log rocketchat

docker-compose.yml file

``` docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES c7139f6a7545 rocketchat/rocket.chat:latest "bash -c 'for i in `…" 17 minutes ago Up 17 minutes 0.0.0.0:4000->3000/tcp rocketchat 60526220ed91 mongo:4.0 "docker-entrypoint.s…" 17 minutes ago Up 17 minutes 27017/tcp mongo ```


_ar _2019-07-22_[edit | edit source]

The rocketchat service is set to run on port 4000 inside the container. The `docker-compose.yml` file specified that port 3000 in the container should be forwarded to 4000 on the host. I changed the port forwarding line in said file to forware port 4000 in the container to 4000 on the host (changed line 30 from `- 4000:3000` to `- 4000:4000`). I then ran `docker-compose down` followed by `docker-compose up` to use the new settings. I think this worked since chat.noisebridge.net is back up now.




James

Rad, it is up and running! Self registration is auto-approved, optional e2e encryption is enabled for private rooms, and anonymous users are allowed read + comment access on public rooms like this one.

Some possible Todos for anyone feeling like getting their hands dirty…

- Sort out basic SMTP email settings

- Check out errors in `docker logs rocketchat`

- Sort out Jitsi video calling and and maybe schedule livechat calling for weekly meetings + 5mof, then embed into our website.

- Enable Slack integration

- Create some bots

- Enable Youtube live streaming or NGALAC

- Enable Federation to other Rocket.chat instances, such as peoplesopen.net/chat

- Enable IRC Federation to connect with Noisebridge and Sudoroom IRC channels.

- Add Giphy support plugin

- Add custom Emojis and custom sounds

- Enable Github, Google, Facebook, Discourse, Meteor (remote Rocket.chat), Twitter login via Oauth

- Trello support