Changes

Jump to navigation Jump to search
283 bytes removed ,  10:04, 30 August 2017
m
→‎Installation: update version
Line 7: Line 7:  
These instructions are for SME Server '''9.0''' 64-bit only.
 
These instructions are for SME Server '''9.0''' 64-bit only.
   −
Prosody is available from the [[epel|'''epel''']] repository, so you have to enable the [[epel|'''epel''']] repository. Epel only holds the 0.8.x series of Prosody, to install or upgrade to the latest 9.x series of Prosody see below instructions.
+
Prosody (v0.9.12-1) is available from the [[epel|'''epel''']] repository, so you have to enable the [[epel|'''epel''']] repository. After enabling the [[epel|epel]] repository, prosody can be installed with:
After enabling the [[epel|epel]] repository, prosody can be installed with:
+
  yum install prosody lua-ldap lua-event --enablerepo=epel
  yum install prosody lua-ldap --enablerepo=epel
  −
 
      
==Configuration==
 
==Configuration==
Line 16: Line 14:  
To automatically start Prosody at boot and configure the ports:
 
To automatically start Prosody at boot and configure the ports:
 
  ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S99prosody
 
  ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S99prosody
  config set prosody service status enabled access private TCPPort 5222 UDPport 5222
+
  config set prosody service  
 +
config setprop prosody status enabled
 +
config setprop prosody access private
 +
config setprop prosody TCPPort 5222
 +
config setprop prosody UDPPort 5222
 +
You can toggle the ''access'' property to enable public/private access.
 +
 
 +
 
 +
 
 +
Then to apply the new service:
 
  signal-event remoteaccess-update
 
  signal-event remoteaccess-update
You can toggle the access property to enable public/private access.
+
 
    
===Configuration file===
 
===Configuration file===
 
Prosody's configuration file is located at:
 
Prosody's configuration file is located at:
 
  /etc/prosody/prosody.cfg.lua
 
  /etc/prosody/prosody.cfg.lua
 +
{{Note box|Please note that the latest version now has split configuration files. One for server wide settings and one for each virtual host. So the below example config file should be adjusted accordingly.}}
 +
 
The basic settings you have to change to run your prosody server on your domain (replace "example.com" with "yourdomain.com"):
 
The basic settings you have to change to run your prosody server on your domain (replace "example.com" with "yourdomain.com"):
 
  admins = {"admin@yourdomain.com"}
 
  admins = {"admin@yourdomain.com"}
Line 43: Line 52:  
TBA
 
TBA
   −
  −
==Prosody version 0.9.x==
  −
TBA
  −
cd /root
  −
wget http://ftpsrv01.networklab.ca/centos/6/RPMS/x86_64/prosody-0.9.4-2.el6.x86_64.rpm
  −
wget http://ftpsrv01.networklab.ca/centos/6/RPMS/x86_64/lua-bitop-1.0.2-1.el6.x86_64.rpm
  −
wget http://ftpsrv01.networklab.ca/centos/6/RPMS/x86_64/lua-sec-0.4.1-6.el6.x86_64.rpm
  −
wget http://ftpsrv01.networklab.ca/centos/6/RPMS/x86_64/luajit-2.0.2-9.el6.x86_64.rpm
  −
wget http://ftpsrv01.networklab.ca/centos/6/RPMS/x86_64/lua-zlib-0.2-1.el6.x86_64.rpm
  −
yum localinstall *.rpm --enablerepo=epel
      
==Documentation==
 
==Documentation==

Navigation menu