my server's running cpanel, want to install subversion and trac

sneakyimp · 12-15-2009, 08:20 PM

My server has cpanel installed. Much as I loathe these virtualized systems, my boss insists we use it for the conveniences it provides.

I've been tasked with setting up Subversion and trac on the server and located some assistance here:
http://www.daniel-skinner.co.uk/setu...s-5/06/01/2008

I was hoping a more experienced person might be able to tell me if I risk any conflicts with cpanel if install subversion and mod_dav_svn using yum install as root:

Code:

yum install subversion mod_dav_svn

Also, the instructions have me making changes to the main apache config, /etc/httpd/conf/httpd.conf. E.g.:

Code:

LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so

There are many other such changes in the main apache conf and I'm wondering if this would a) work and perhaps b) break my whole cpanel setup.

Any advice here would be greatly appreciated.

sneakyimp · 12-19-2009, 01:05 PM

Alright so my boss told me to go ahead with the install instructions and as it turns out, the repository commands (YUM, RPM) aren't really working. Apparently because the system uses WHM/CPanel, the system has not been tracking installed software using the repository type stuff. In other words, YUM thinks there is no install of apache on this machine:

Code:

[root@host.domain.com] ~ >> rpm -q httpd
package httpd is not installed

Some further research yielded this forum posting with instructions for
this install in a WHM/CPanel environment:
http://www.edugeek.net/forums/nix/26...anel-11-a.html

Does anyone have experience with this? Any advice would be much appreciated.

Elv13 · 12-19-2009, 01:53 PM

Unzip the rpm and all the required dependencies and install them by hand. It is not a good solution at all, but it will work if it is well done.

The best solution would create a downtime. On a new drive, install a clean RedHat/CentOS, then create a rpm package for your cpanel requiring the real apache and not the static copy it seem to have installed, then install svn and replace the production server with the new one. Having an unmanaged server with uniknow static build source is more risky than installing subversion by hand. Many remote exploit bugs have been closed over the years in apache, and most of them have been backported to RedHat, it is safer just to do something clean.