The access model is going to be based on the vBulletin forum login and passwords, we are still debating on how to handle this correct way, but Brent will write the trac side and I will write forum site of identification process. For now the only once that can really do anything interesting are Brent and I.

Here are some of the details of our setup.
The server it self is a virtual server for easy snapshots and maintaince. It’s running debian as our base.
We use apache2 with mod_python and 3 virtual host.

1. http://trac.4theweb.nl running track.
2. http://svn.4theweb.nl running the subversion.
3. default virtual host what needs to be worked out.

The beauty of this setup is, you always start with this base url and just append the project name on both svn and trac and you are there. “http://trac.4theweb.nl/joomlalib” or “http://svn.4theweb.nl/joomlalib” for example.

I’ll write up a some more when configuration is complete and I have worked with the setup in production but compared too the Joomla! forge it is more easy and way faster.

Wooh, trac is a nice sleek program to manage your projects and after again working with the Joomla forge and waiting 10 sec every page impression. I’m sold.
I’m planning to divided my server in 2 virtual servers, and decicated one to our projects(Joomlalib,BSQ_sitestats,Gallery 2 bridge and ….). This will be faster and easier to maintain then using our current setup, we will merge our wiki into trac and clear another upgrade job.

Only one thing stands in our way, I have to go to the server to put in another disk before I can do this and time is limited at the moment.