Template:AddReposRHEL: Difference between revisions

From Open-Xchange
No edit summary
(→‎Add Open-Xchange Repository: Adjusted to 6.22 paths on s.o.c)
Line 9: Line 9:
  $ vim /etc/yum.repos.d/ox.repo
  $ vim /etc/yum.repos.d/ox.repo
   
   
  [ox]
  [ox-backend]
  name=Open-Xchange
  name=Open-Xchange
  baseurl=http://software.open-xchange.com/OX6/stable/{{{rhelname}}}/
  baseurl=http://software.open-xchange.com/OX6/6.22/backend/{{{rhelname}}}/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m
 
[ox-frontend]
name=Open-Xchange
baseurl=http://software.open-xchange.com/OX6/6.22/frontend/{{{rhelname}}}/
  gpgkey=http://software.open-xchange.com/oxbuildkey.pub
  gpgkey=http://software.open-xchange.com/oxbuildkey.pub
  enabled=1
  enabled=1

Revision as of 10:31, 12 September 2012

Add Open-Xchange Repository

Open-Xchange maintains public available software repositories for different platforms, such as RHEL. This repository should be added to the RHEL installation to enable simple installation and updates.

Start a console and create a software repository file for Open-Xchange:

$ vim /etc/yum.repos.d/ox.repo

[ox-backend]
name=Open-Xchange
baseurl=http://software.open-xchange.com/OX6/6.22/backend/{{{rhelname}}}/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m
[ox-frontend]
name=Open-Xchange
baseurl=http://software.open-xchange.com/OX6/6.22/frontend/{{{rhelname}}}/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m
# if you have a valid maintenance subscription, please uncomment the 
# following and add the ldb account data to the url so that the most recent
# packages get installed

[ox-updates]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/{{{rhelname}}}/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

In case there are issues with an username and password containing URL unsafe characters, e.g. an @, they have to be entered URL encoded. Details can be found at http://www.w3schools.com/tags/ref_urlencode.asp