>
>> If the system is correctly documented and occasionally tested
>> we should be able to do this.
>
> What I'd like to see is a master svn repository for gforge code that
> we use. that plus database backups would make for easy restore or
> failover if we have issues. To not use source control on our changes
> to the gforge code seems a bit silly. Of course this should be
> isolated on a different machine than the gforge machine.
Well I am 100% for that! I can set up a trac and everything!
> Hey now, don't knock Gentoo. I was a slackware user since 1994 and
> switched to Gentoo a few years back. I love it. It's not like it's
> lfs and portage is pretty damn powerful. ;-) Don't let those
> funroll-loops guys fool you, it can be serious on the server side too.
I have you beat... I started with SLS (what Slackware was based off of)
and in general I don't have a problem with Gentoo but I would not use
it in a production server environment. I love using it for development.
Sincerely,
Joshua D. Drake
>
> Gavin M. Roy
> 800 Pound Gorilla
> gmr@ehpg.net
>
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: PLphp, PLperl - http://www.commandprompt.com/
