Koozali.org: home of the SME Server

Contribs.org Forums => General Discussion => Topic started by: soprom on September 26, 2010, 03:58:45 AM

Title: Temporary Install Method for ejabberd
Post by: soprom on September 26, 2010, 03:58:45 AM

Here are the steps I did to install ejabberd on SME8b6. When the contrib will be made available, it should be done as per wiki.

Code: [Select]

# Add repo for dependencies
db yum_repositories set epel repository \
EnableGroups no \
GPGCheck yes \
MirrorList "http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=\$basearch" \
Name "Epel" \
Visible yes \
status disabled

# apply this change
signal-event yum-modify

# Get rpm
mkdir /root/ejabberd
cd /root/ejabberd
wget http://distro.ibiblio.org/pub/linux/distributions/smeserver/contribs/jpl/smecontribs/smeserver-ejabberd/smeserver-ejabberd-2.0.1-1.el4.sme.noarch.rpm

# Install
yum localinstall smeserver-ejabberd-2.0.1-1.el4.sme.noarch.rpm --enablerepo=epel

# Initialize
/etc/e-smith/events/actions/initialize-default-databases
/etc/e-smith/events/actions/navigation-conf
The server-manager has a config page and ejabberd has its own admin page at http://local-ip:5280/admin/

Yum reports these changes:

Code: [Select]

-------------------------------------------------------------------------
Installed:
  smeserver-ejabberd.noarch 0:2.0.1-1.el4.sme                                                                                             

Dependency Installed:
  ejabberd.i386 0:2.1.5-6.el5
  erlang.i386 0:R12B-5.10.el5             
  erlang-esasl.i386 0:0.1-5.el5 
  libX11.i386 0:1.0.3-11.el5   
  libXau.i386 0:1.0.1-3.1     
  libXdmcp.i386 0:1.0.1-2.1             
  tcl.i386 0:8.4.13-4.el5       
  tk.i386 0:8.4.13-5.el5_1.1   
  unixODBC.i386 0:2.2.11-7.1   
  xorg-x11-filesystem.noarch 0:7.1-2.fc6   
-------------------------------------------------------------------------

Title: Re: Temporary Install Method for ejabberd
Post by: byte on September 28, 2010, 01:03:36 PM

Moving this topic to the General Discussion forum, it is more appropriate there. Thanks