Changes

From SME Server
Jump to navigationJump to search
387 bytes added ,  09:30, 29 August 2016
m
Undo revision 32080 by RequestedDeletion (talk)
Line 112: Line 112:     
{{Note box|Please note that if you change anything on your Rocket.Chat environment such as URL's, subdomain name(s), ports or mail server, you have to run the above again to reflect your new environment. If so, please remove /etc/rc.d/init.d/rocketchat first. (rm /etc/rc.d/init.d/rocketchat).}}
 
{{Note box|Please note that if you change anything on your Rocket.Chat environment such as URL's, subdomain name(s), ports or mail server, you have to run the above again to reflect your new environment. If so, please remove /etc/rc.d/init.d/rocketchat first. (rm /etc/rc.d/init.d/rocketchat).}}
 +
 +
====Create SME Server service link====
 +
Now we can create a link to the SME Server way of starting services automatically at boot time or manually:
 +
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99rocketchat
 +
 +
and you can start/stop/status your rocketchat service e.g.:
 +
service rocketchat status
 +
service rocketchat start
 +
service rocketchat stop
 +
service rocketchat restart
    
Please note that it may take a little while, up to a minute, for rocketchat to become available. In the mean time you can be shown a HTTP error 503. Please try again in a minute or a bit longer. Why this is? No Idea for now, other that it may be related to MongoDB processes.
 
Please note that it may take a little while, up to a minute, for rocketchat to become available. In the mean time you can be shown a HTTP error 503. Please try again in a minute or a bit longer. Why this is? No Idea for now, other that it may be related to MongoDB processes.
 +
 +
    
==Make Rocket.Chat available on a sub domain==
 
==Make Rocket.Chat available on a sub domain==

Navigation menu