Changes

First we need to create the SME Server services:

First we need to create the SME Server services:

For Rocket.Chat

For Rocket.Chat:

  ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99rocketchat

  ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99rocketchat

  config set rocketchat service status enabled TCPPort 3000 access public

  config set rocketchat service status enabled TCPPort 3000 access public

  signal-event remoteaccess-update

  signal-event remoteaccess-update

For MongoDB (please note the usage of mongod and NOT mongod'''b''')

For MongoDB (please note the usage of mongod and NOT mongod'''b'''):

  ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99rh-mongodb26-mongod

  ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99rh-mongodb26-mongod

  config set rh-mongodb26-mongod service status enabled access private TCPPort 27017

  config set rh-mongodb26-mongod service status enabled access private TCPPort 27017

{{Note box|This FIRST user will be the 'master administrator' even if you use [[Rocket_Chat#LDAP_Authentication|'''LDAP authentication''']] for your users. So if even if you use LDAP, this user will still be able to login and grant Rocket.Chat admin rights to [[Rocket_Chat#LDAP_Authentication|LDAP]] accounts.}}

{{Note box|This FIRST user will be the 'master administrator' even if you use [[Rocket_Chat#LDAP_Authentication|'''LDAP authentication''']] for your users. So if even if you use LDAP, this user will still be able to login and grant Rocket.Chat admin rights to [[Rocket_Chat#LDAP_Authentication|LDAP]] accounts.}}

==Auto start Rocket.Chat at boot==

==Auto start Rocket.Chat at boot==