Install Mono on CentOS 5.4 without blowing ISPConfig 3
 

I have done the "Perfect Setup" for ISPConfig 3 and CentOS 5.4 and have a few sites up and running. Now, I'd like install Mono and configure one site to use it, so I can drop in a .NET site.

I found the following post from 2007 for installing/configuring on Ubuntu, but I can't seem to find any install notes specifically for ISPConfig and CentOS:
http://www.howtoforge.com/forums/arc...p/t-16141.html

and the following for a generic Mono install on CentOS:
http://poormanstech.blogspot.com/200...ling-mono.html

Can I follow the Mono install and then add Apache directives from the howtoforge post without blowing my ISPConfig install? What config files should I backup? I don't have /etc/apache2, but I do have /etc/httpd/conf/sites-enabled. Should I backup the vhosts file there?

Thanks in advance!

Do you not have a production and test server? It might behoove you to look into a test server. If nothing else, make a virtual machine of it. Linux VM's don't require too many resources.

Aside from this, mod_mono is just a plugin for the httpd server. You can just install it and restart httpd. Configuration is as simple as setting a location tag as and its handler in httpd.conf (/etc/httpd/conf/httpd.conf).

<Location /test>
SetHandler mono
</Location>

As long as you don't have SELinux running, it should be fairly simple.

this is my test server.

update: i found newer postings for installing mono, xsp and mod_mono. i think i have everything but maybe the directives correct.

you may view everything i've done over at howtoforge.com forums

http://www.howtoforge.com/forums/showthread.php?t=40881

im receiving 500 internal errors that may be related to permissions problems. but i still cant figure it out.

thanks!

500 errors are generally fed in place of leaking source code. Check /var/log/httpd/error_log for output. It will probably refer you to a PAM module. I am a Fedora user, so I base my experience off of this. Any ASP issues may be source code related. On of the easiest ways to test this is to start xsp2 --root (anAspDir) --port (port). Then you can check it locally, and it should output error messages for you. The port number should be something like 8081 to keep from intruding on other services and such.