Line 285: |
Line 285: |
| [[Category: Webapps]] | | [[Category: Webapps]] |
| | | |
− |
| |
− | ==smeserver-rocketchat contrib==
| |
− | {{WIP box}}
| |
− | This contrib aims to reduce some of the setup for rocketchat and add some flexibility with settings
| |
− |
| |
− | Add repos:
| |
− |
| |
− | * [[epel]]
| |
− | * [[Centos-sclo-rh]]
| |
− | * [[User:ReetP|reetp]]
| |
− |
| |
− | yum install rh-python34-python rh-mongodb26-mongodb rh-mongodb26-mongodb-server nodejs010 GraphicsMagick --enablerepo=centos-sclo-rh,epel
| |
− |
| |
− | scl enable nodejs010 bash
| |
− | npm install -g inherits
| |
− | npm install -g n
| |
− | n 0.10.40
| |
− | exit
| |
− |
| |
− | cd /root
| |
− | curl -L https://rocket.chat/releases/latest/download -o rocket.chat.tgz
| |
− | tar zxvf rocket.chat.tgz
| |
− | mv bundle /opt/Rocket.Chat
| |
− |
| |
− | cd /opt/Rocket.Chat/programs/server
| |
− | npm install
| |
− | npm install -g forever
| |
− |
| |
− | patch mailcomposer.js to add From header. You can use this from wherever the patch file is (where should it be ?):
| |
− | patch -p0 -i /opt/mailcomposer.patch
| |
− |
| |
− | Install rocket chat contrib:
| |
− |
| |
− | yum enablerepo=reetp install smeserver-rocketchat
| |
− |
| |
− | db setprop rocketchat status enabled
| |
− |
| |
− | signal-event post-upgrade;signal-event reboot
| |
− |
| |
− | DB settings
| |
− |
| |
− | rocketchat=service
| |
− | TCPPort=3000
| |
− | access=public
| |
− | mailPort=25
| |
− | mailURL=localhost
| |
− | status=enabled
| |
− |
| |
− | rh-mongodb26-mongod=service
| |
− | TCPPort=27017
| |
− | access=private
| |
− | mongoURL=localhost
| |
− | status=enabled
| |
− |
| |
− | BEFORE we login for the first time we need to set up mail settings correctly:
| |
− |
| |
− | From bash:
| |
− |
| |
− | mongo rocketchat --eval 'db.rocketchat_settings.update({"_id" : "SMTP_Host"}, {$set: {"value":"localhost"}});'
| |
− | mongo rocketchat --eval 'db.rocketchat_settings.update({"_id" : "From_Email"}, {$set: {"value":"admin@yourdomain.com"}});'
| |
− |
| |
− | We can check the individual values set like this:
| |
− |
| |
− | mongo rocketchat --eval 'db.rocketchat_settings.find({"_id":"From_Email"}, {_id:0, value:1}).shellPrint();'
| |
− | mongo rocketchat --eval 'db.rocketchat_settings.find({"_id":"SMTP_Host"}, {_id:0, value: 1}).shellPrint();'
| |
− |
| |
− | All values per _id:
| |
− | mongo rocketchat --eval 'db.rocketchat_settings.find({"_id" : "SMTP_Host"}).shellPrint();'
| |
− | mongo rocketchat --eval 'db.rocketchat_settings.find({"_id" : "From_Email"}).shellPrint();'
| |
− |
| |
− |
| |
− | Now restart rocketchat to reread the DB settings:
| |
− |
| |
− | service rocketchat restart
| |
− |
| |
− | Login at http://yourdomain:3000
| |
− |
| |
− | It will first get you to create an admin user.
| |
− |
| |
− | If you have an issue with no email sent/received then login using the email address and password you just set
| |
− |
| |
− | ===Bugs===
| |
− |
| |
− | Look for bugs :-) As the contrib is not in CVS please report them in the forum
| |
− |
| |
− | ===SSL - in progress===
| |
− |
| |
− | You will need smeserver-rocketchat-0.1-4
| |
− |
| |
− | We need some extra settings to enable SSL with ProxyPass.
| |
− |
| |
− | First install proxy pass rpm:
| |
− |
| |
− | yum --enablerepo=fws install mod_proxy_wstunnel
| |
− |
| |
− | Regenerate httpd.conf
| |
− |
| |
− | signal-event remoteaccess-update
| |
− |
| |
− | Now we need to setup our subdomain
| |
− |
| |
− | db domains set chat.mycompany.local domain Description RocketChat Nameservers internet \
| |
− | TemplatePath ProxyPassVirtualRocketchat ProxyPassTarget http://localhost:3000/
| |
− |
| |
− | It should look like this:
| |
− |
| |
− | chat.mycompany.local=domain
| |
− | Nameservers=internet
| |
− | ProxyPassTarget=http://127.0.0.1:3000/
| |
− | TemplatePath=ProxyPassVirtualRocketchat
| |
− |
| |
− |
| |
− | We need to set Rocketchat to listen on localhost now:
| |
− |
| |
− | config setprop rocketchat rootURL localhost
| |
− | signal-event remoteaccess-update
| |
− | service rocketchat restart
| |
− |
| |
− | If you can now successfully get to Rocketchat on your subdomain https://chat.mycompany.local you can disable default access on port 3000:
| |
− |
| |
− | config setprop rocketchat access private
| |
− | signal-event remoteaccess-update
| |
| | | |
| ==Letsencrypt support== | | ==Letsencrypt support== |