Let me preface this with the fact that if you're running one of the already supported OSs (debian or unbuntu for instance) you shouldn't follow this guide - instead you should just look on the mono website for information.

First thing I did was grab the most up-to-date mono and xst sources (i matched versions)

cd /tmp
wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.6.tar.bz2
wget http://ftp.novell.com/pub/mono/sources/mod_mono/mod_mono-2.6.tar.bz2
wget http://ftp.novell.com/pub/mono/sources/xsp/xsp-2.6.tar.bz2

Then unpack everything

tar -jxvf mono-2.6.tar.bz2
 tar -jxvf xsp-2.6.tar.bz2
 tar -jxvf mod_mono-2.6.tar.bz2

then build mono first (change anything on the ./configure line to your liking, I do suggest picking a place to put mono, letting it install wherever it wants to makes the rest of the process very painful!):

cd /tmp/mono-2.6
./configure --prefix=/opt/mono
make ; make install
echo export PKG_CONFIG_PATH=/opt/mono/lib/pkgconfig:$PKG_CONFIG_PATH>>~/.bash_profile
echo export PATH=/opt/mono/bin:$PATH>>~/.bash_profile
source ~/.bash_profile

after a bit you'll have mono installed

Now build xsp (i had to add pkgconfig to an environment variable to get it to work)

cd /tmp/xsp-2.6
./configure --prefix=/opt/mono
make ; make install

Finally build mod_mono, you'll probably need to tell it where apache's apr-config is... it took a while for me to find it.. heh

find / -iname apr*config
cd /tmp/mod_mono-2.6
./configure --prefix=/opt/mono --with-mono-prefix=/opt/mono --with-apr-config=/usr/bin/apr-1-config
make ; make install

you should now find mod_mono in your apache modules dir (in my case /usr/lib64/httpd/modules/)

ls /usr/lib64/httpd/modules/mod_mono*
17 Feb  5 22:54 /usr/lib64/httpd/modules/mod_mono.so -> mod_mono.so.0.0.0
145511 Feb  5 22:54 /usr/lib64/httpd/modules/mod_mono.so.0.0.0

the mod_mono install seems to have automatically created mod_mono.conf in my httpd/conf folder, but you may want to make sure it's there

vim /etc/httpd/conf/mod_mono.conf

# mod_mono.conf

# Achtung! This file may be overwritten
# Use 'include mod_mono.conf' from other configuration file
# to load mod_mono module.

<IfModule !mod_mono.c>
    LoadModule mono_module /usr/lib64/httpd/modules/mod_mono.so
</IfModule>

<IfModule mod_headers.c>
    Header set X-Powered-By "Mono"
</IfModule>

AddType application/x-asp-net .aspx
AddType application/x-asp-net .asmx
AddType application/x-asp-net .ashx
AddType application/x-asp-net .asax
AddType application/x-asp-net .ascx
AddType application/x-asp-net .soap
AddType application/x-asp-net .rem
AddType application/x-asp-net .axd
AddType application/x-asp-net .cs
AddType application/x-asp-net .vb
AddType application/x-asp-net .master
AddType application/x-asp-net .sitemap
AddType application/x-asp-net .resources
AddType application/x-asp-net .skin
AddType application/x-asp-net .browser
AddType application/x-asp-net .webinfo
AddType application/x-asp-net .resx
AddType application/x-asp-net .licx
AddType application/x-asp-net .csproj
AddType application/x-asp-net .vbproj
AddType application/x-asp-net .config
AddType application/x-asp-net .Config
AddType application/x-asp-net .dll
DirectoryIndex index.aspx
DirectoryIndex Default.aspx
DirectoryIndex default.aspx

Now, you need to get this to work with ISPConfig3, since if you've followed my other tutorials, that's what you have running things on the back end.

Modify your httpd.conf file to include mod_mono.conf. You want to do this at the very bottom, just before the NameVirtualHost directives (ISPConfig puts 3 directives at the very bottom of httpd.conf, you want to place this line just before them:

vim /etc/httpd/conf/httpd.conf

Include /etc/httpd/conf/mod_mono.conf
# this is where ISPConfig's stuff is, don't modify it, this comment is so you know where to put the line above the comment 
NameVirtualHost *:80
NameVirtualHost *:443
Include /etc/httpd/conf/sites-enabled/

now, restart apache

service httpd restart

and open up ISPConfig. go to sites > website > Select the website you want to add a mono enabled directory to, then click on the "Options" tab for that site. Enter the following into the Apache Directives (replace /var/www/path/to/the/web/folder with the path to that site's web folder)

MonoPath default "/opt/mono/lib/mono/2.0"
MonoServerPath default /opt/mono/bin/mod-mono-server
AddMonoApplications default "/test:/var/www/path/to/the/web/folder/test"
<location /test>
	MonoSetServerAlias default
	SetHandler mono
</location>

and finally restart httpd

service httpd restart

here's a test page, create it in your /var/www/path/to/the/web/folder/test directory and set the permissions to whatever the other site's permissions are, or apache.apache

<html>
<body>
<% Response.Write("Hello World!"); %>
</body>
</html>

now, once ISPConfig restarts apache (sometimes this is instant but i've seen it take up to 5 minutes) you'll see Hello World! displayed

First, you need to install subversion - it was automatically installed for me already when I installed the OS, however I wanted to update it and found out that I couldn't do so until I deleted the i386 version.

Don't do this step if you're on a 32-bit system!

yum erase subversion.i386

Next, you can install or upgrade subversion and add mod_dav_svn

yum install subversion mod_dav_svn

And Trac...

yum install python
cd /tmp
wget http://peak.telecommunity.com/dist/ez_setup.py
python ez_setup.py
yum install mod_python

MySQL-python is needed for python to interact with mysql. Download the latest MySQL-python from http://sourceforge.net/projects/mysql-python, then:

tar -zxvf mysql-python-tarball.tar.gz
cd mysql-python-source-directory
python setup.py build && python.setup.py install

Some developer packages will also be needed:

yum install neon neon-devel python-devel swig

Next, install clearsilver. You should look for the version that works for your OS. For CentOS 5, it's the latest el5.rf, and either i386 or x86 depending on your setup. You can find the list of packages here: http://dag.wieers.com/rpm/packages/clearsilver/. Make sure that you get the same version number of clearsilver and python-clearsilver.

wget http://dag.wieers.com/rpm/packages/clearsilver/clearsilver-VERSION.el5.rf.ENVIRONMENT.rpm
rpm -i clearsilver-VERSION.el5.rf.ENVIRONMENT.rpm
wget http://dag.wieers.com/rpm/packages/clearsilver/python-clearsilver-VERSION.el5.rf.ENVIRONMENT.rpm
rpm -i python-clearsilver-VERSION.el5.rf.ENVIRONMENT.rpm

Now that you have all of these, you can install Trac. Download the latest tar from http://trac.edgewall.org/wiki/TracDownload

cd /tmp
wget http://path.to/TracDownloadTarball.tar.gz
tar -zxvf TracDownloadTarball.tar.gz
cd TracDownloadTarball
python ./setup.py install

You're done.

Create SVN Repositories and link new Trac projects to them. You'll first make directories to place your svn and trac projects (i'm using /var/www/svn|trac)

mkdir /var/www/svn/svn-repository-name
mkdir /var/www/trac/svn-repository-name
svnadmin create --fs-type fsfs /var/www/svn/svn-repository-name
trac-admin /var/www/trac/
initenv
chown -R apache.apache /var/www/svn/svn-repository-name
chown -R apache.apache /var/www/trac/svn-repository-name

Now you'll need to make a subversion.conf file for apache to load up. One might already exist (it did in my case), but even if it doesn't, that's ok.

vim /etc/httpd/conf.d/subversion.conf

LoadModule dav_svn_module     modules/mod_dav_svn.so
LoadModule authz_svn_module   modules/mod_authz_svn.so
<VirtualHost *:80>
	ServerName svn.astrosmurf.com
	DocumentRoot /path/to/existing/empty/directory
	<Location />
		DAV svn
		SVNParentPath /path/to/svn/root
		SVNListParentPath on
		Order allow,deny
		Allow from all
	</Location>
	<LocationMatch /.+>
		# access differences per repository in here:
		AuthzSVNAccessFile /path/to/svn/root/svn-acl-conf

		# means to authenticate the user
		AuthType Basic
		AuthName "Astrosmurf Subversion"
		AuthUserFile /path/to/svn/root/svn.htpasswd

		# only authenticated users may access the repository
		Require valid-user
	</LocationMatch>
	ErrorLog /var/www/logs/error.svn.log
	CustomLog /var/www/logs/access.svn.log combined
</VirtualHost>

You'll also want to do the same for Trac

vim /etc/httpd/conf.d/trac.conf

and the contents should look similar to this (of course, modify both of these to suit your needs):

<IfModule mod_python.c>
	<VirtualHost *:80>
		ServerName trac.yourserver.com
		DocumentRoot /path/to/existing/empty/directory
		<Location />
			SetHandler mod_python
			PythonInterpreter main_interpreter
			PythonHandler trac.web.modpython_frontend
			PythonOption TracEnvParentDir /path/to/trac/root
			PythonOption TracUriRoot /
			PythonOption PYTHON_EGG_CACHE /usr/lib/trac/plugins-cache
			Order allow,deny
			Allow from all
		</Location>
		<LocationMatch /[^/P]+/.*>
			# means to authenticate the user
			AuthType Basic
			AuthName "Subversion"
			AuthUserFile /path/to/svn/root/svn.htpasswd
			AuthGroupFile /path/to/svn/root/svn-authgroup-conf
			# only authenticated users may access the repository
			Require group staff
		</LocationMatch>
		<LocationMatch /Pub[^/]+/.*>
			# means to authenticate the user
			AuthType Basic
			AuthName "Subversion"
			AuthUserFile /path/to/svn/root/svn.htpasswd
			# only authenticated users may access the repository
			Require valid-user
		</LocationMatch>

		ErrorLog /var/www/logs/error.trac.log
		CustomLog /var/www/logs/access.trac.log combined
	</VirtualHost>
</IfModule>

Now, make the different auth files. This file contains users and groups... in fact I don't remember why i have both the acl and the authgroup file, but whatever...

vim /var/www/svn/svn-acl-conf

[groups]
staff = user1, user2, user3
rb = reviewboard

[/]
@rb = rw

[name_of_staff_repo:/]
@staff = rw

[name_of_user1_repo:/]
user1 = rw

[Public:/]
@staff = rw
public = r

and set up authgroup. This file contains group names and who belongs to them

vim /var/www/svn/svn-authgroup-conf

staff: user1 user2 user3

And the passwords file

touch /var/www/svn/svn.htpasswd
htpasswd -m /var/www/svn/svn.htpasswd user1
htpasswd -m /var/www/svn/svn.htpasswd user2
htpasswd -m /var/www/svn/svn.htpasswd user3

You can also create a public user and somehow let the public know that they can enter your repository with username public and password public.

htpasswd -m /var/www/svn/svn.htpasswd public

Restart httpd and you should should now be able to go to http://svn.yourhost.com/ and http://trac.yourhost.com/

service httpd restart

A lot of this info came from several different sources, some from googling and others form these places:

• http://biotext.org.uk/updating-subversion-on-64-bit-linux-centos-5/
• http://www.daniel-skinner.co.uk/setup-subversion-and-trac-on-centos-5/06/01/2008
• http://www.techyouruniverse.com/software/installing-trac-with-subversion-on-cent-os-5-with-neon-and-quicksilver

Setting up Postfix to use your ISP's smtp

Note: if your ISP requires authentication for smtp, you'll have to do some googleing.  If they don't (mine doesn't) then this will work fine for you.

vim /etc/postfix/main.cf

Next, you need to add the relayhost variable, you may have to enclose the domain in brackets, I didn't have to but I've read everywhere that you should:

relayhost = [your.isps.smtp.com]

Other items to potentially edit:

myhostname = your.host.name
mydomain = your.domain
myorigin = $mydomain
inet_interfaces = all
mydestination = $myhostname, localhost.$mydomain, localhost
unknown_local_recipient_reject_code = 550
relay_domains = $mydestination

Now, restart postfix

service postfix reload

Forwarding name@yourdomain.com to a real e-mail address

First things first, you need to edit main.cf

vim /etc/postfix/main.cf

Next, either add or edit the following lines. You can add as many domains as you want. If you followed the Perfect Server tutorial, you'll have all sorts of junk in these variables, just replace them.

virtual_alias_domains = yourdomain.com yourotherdomain.com.
virtual_alias_maps = hash:/etc/postfix/virtual

Now, edit the /etc/postfix/virtual file to add your forward rules:

vim /etc/postfix/virtual

forward all mail sent to *@yourdomain.com to your@email.com and name@yourotherdomain.com to your@email.com:

@yourdomain.com your@email.com
name@yourotherdomain.com your@email.com

Now, restart postfix

postmap /etc/postfix/virtual
service postfix reload

First, you're going to need the LinuxDrivers zip file.  You'll need to unzip and then unrar l1e-l2e-linux-v1.0.0.4.rar (found in the LinuxDrivers/L1e_Lan directory in the zip).  I had to do this on my Windows PC since I couldn't install unrar on the server (no network, remember?)

Once you're transfered the contents of l1e-l2e-linux-v1.0.0.4.rar to the server, follow these steps:

su -
cd /path/to/LinuxDrivers/src/
make clean
KBUILD_NOPEDANTIC=1 make clean
KBUILD_NOPEDANTIC=1 make
KBUILD_NOPEDANTIC=1 make install
cd /lib/modules/2.6.18-92.el5xen/kernel/drivers/net/atl1e/
mv atl1e.ko atl1e.ko.old
mv /path/to/LinuxDrivers/src/atl1e.ko atl1e.ko
insmod ./atl1e.ko

Once that is done, reboot your server and then configure your network however you need to. If all goes well, you should have eth0. I remember the first time I set this server up I attempted to install an incorrect driver that was on the installation disc. This caused me a lot of headaches when it came to installing the correct driver. This time I ignored network all together during setup and I was pleasantly surprised how easy it was to build and install the drivers this time.