Rocket.Chat: Difference between revisions

From Bitpost wiki
Line 40: Line 40:
===== Set up a systemd service =====
===== Set up a systemd service =====


See example on jaws.
# Uninstall snap if needed
sudo snap remove rocketchat-server
 
* Create a service file in your config folder, and stow it into /etc/systemd/system.  See example on jaws.
* Install it
sudo systemctl daemon-reload
sudo systemctl start rocketchat
# Give it a GOOD 5 MINUTES to start up, sigh... once it does:
sudo systemctl enable rocketchat


==== Now FINISH UP ====
==== Now FINISH UP ====

Revision as of 14:09, 7 June 2021

Server is running, ask Mikey to get you registered at the "secret" registration url.

Clients

The Linux and android clients are tested and working out of the box. How nice.

Docs

Server maintenance

  • To update:
ssh jaws
sudo apt snap refresh
sudo service snap.rocketchat-server.rocketchat-server restart

This supposedly happens "automagically"...? Also, snap updates lag behind release updates. Whatevs.

Server installation

Snap install is a clusterfuck of imperfection... DO NOT SEEK THE TREASURE!

From source

sudo apt-get install -y git build-essential mongodb nodejs graphicsmagick
cd ~/apps
git clone https://github.com/RocketChat/Rocket.Chat.git
cd Rocket.Chat
curl https://install.meteor.com/ | sh
meteor npm install
meteor npm start

Make sure that gets going. Once it does, there are two more optional steps.

Install system mongo

If you want to use a full system mongo installation instead of the dummy one that comes embedded in meteor, you'll need to tell meteor how to find it. It should be configured as a replicaset (even though it's one node):

# install system mongo
# use a startup script like this:
 cd ~/apps/Rocket.Chat.github-source
 MONGO_URL=mongodb://localhost:27017/rocketchat?replicaSet=rs01 MONGO_OPLOG_URL=mongodb://localhost:27017/local?replicaSet=rs01 ROOT_URL=http://localhost:3000/ PORT=3000 meteor npm start
Set up a systemd service
# Uninstall snap if needed
sudo snap remove rocketchat-server
  • Create a service file in your config folder, and stow it into /etc/systemd/system. See example on jaws.
  • Install it
sudo systemctl daemon-reload
sudo systemctl start rocketchat
# Give it a GOOD 5 MINUTES to start up, sigh... once it does:
sudo systemctl enable rocketchat

Now FINISH UP

  • Browse to admin panel at http://yourserver:3000
  • Register with rocket.chat (I think you have to to get mobile updates???)
  • Set up an admin account
  • Update haproxy and certbot to support a subdomain that is publicly available

Configuration

Once you log in as admin, you get a SHITTON of settings to manage. Important ones:

  • Admin > Settings > search > site > CHANGE THE SITE from http://localhost to your FQDN!
  • I updated my admin layout Content. It includes Home page text, TOS etc.
  • Admin > Accounts > Registration > Manually Approve New Users
  • Admin > Accounts > Registration > Registration Form > Secret URL (URL will be /register/(secret)/ )
  • Admin > Layout > User Interface > Allow Special Characters in Room Names > Toggle ON
  • Admin > Search > Default Provider > Global Search ON (to add a toggleable global search option)
  • Admin > Video Conference > Jitsu > Enable (NOTE desktop app doesn't find my camera, but chrome does)
  • Should I? Admin > Accounts > Registration > Use DNS Domain Check

Enable mobile push

This is not as simple as it should be...

  • Admin > Setup Wizard > Cloud Info > Cloud Service Agree Privacy > Toggle ON

YOU MUST restart server for setting to be applied! This apparently sets:

Admin > Settings > Push > Production read-only toggle ON

This is necessary for mobile chat notifications to work!

  • Register for cloud services
  • When creating an account, I did NOT get email confirmation. I had to use "Forgot password" to reset and get access.
  • Click Register Self-managed, and get the token.
  • Admin > Connectivity Services > Register > paste the token
  • Admin > Connectivity Services > Login to Rocket.Chat Cloud
  • Admin > Settings > Push > Send a test push

Holy hell, it worked!