This weekend I installed Cent OS on server #2, and got Collab.Net installed (similar to sourceforge or java.net). It requires a dedicated server with a fresh install of Red Hat Enterprise Linux. Cent OS is a free "100% binary compatible" linux, and following these instructions I tricked the Collab.Net installer into working. It took a few tries though. First I followed the normal instructions which instructs you to install EVERYTHING on Red Hat.. which meant 7 GB of garbage. The Collab.Net setup program complained about a couple things, and searching the net lead me to the Cent OS instructions in a forum. Someone had figured out how to use the Cent OS server cd (single CD), not install the "everything" package, and which things to do before running the Collab.Net setup. I tried it, but it also failed because libzlib wasn't installed. I remembered installing it, and confirmed that it was installed. A second error complained that some i386 folder didn't exist. After further reading I realized that I have to use the Cent OS 3.8 server i386 CD. I don't know if version 4 would work or not. After getting the right version of the OS installed and following the pre-setup instructions from the forum, everything now works.

I logged in and had a quick look around. I love how an admin can add a new project and it automatically sets up a subversion repository, a new project in Project Tracker (based on Scarab, Bugzilla's replacement), mailing lists, forums, and a whole site dedicated to the project. You can manage all users and their permissions through the website. I believe you can expose some parts to registered users such as the main project pages, forums, some mailing lists, etc... but keep subversion and project tracker private to people with certain roles. Looking around I've realized that it's not something I'm going to have working perfectly over the weekend. I'll have to read the manual and play with it over the next couple of weeks to get things set up perfectly.

Before I get too involved with it, I want to try a couple more things to make sure they work. I have finally found a way to get Centric CRM to compile (I was missing a library on my computer), and want to install it on the same application server used by Collab.Net (JBoss). I also want to download JRoller, get it compiled and deployed on the same application server. If I can get all 3 installed and working on the same server then I will dedicate time to each so that I can get to know them and start using them.

The last thing I wanted to install was Scalix, an open source MS Exchange alternative with a very slick web UI. It also requires Red Hat Enterprise Linux and I thought I might be able to trick it into working on Cent OS. This one is a C or C++ program and the community edition requires you to compile it. What I'm most concerned about is how it might clash with Collab.Net's programs. Collab.Net installed qmail to handle the mailing lists, and various other email related features. I'm now thinking Scalix will have to go on it's own computer (or virtual computer).

Originally all of this was going to be installed on Solaris, and the programs that reqired Red Hat would go in a "Solaris Container for Linux". It turns out the container runs Cent OS. I still want to get into Solaris, but it's too much for me right now. I'd have to learn about containers, resource management, unix commands, etc... that will come later this year. It would be great if I could get Collab.Net in one container, Scalix on an other, Centric CRM and JRoller in an other. Centric CRM and JRoller could be in a Solaris container of their own, or deployed into one of the two other existing app servers. I would need several real IP addresses, which cost $10/month each. We'll get there... one day.