I am looking for information as to CVS server best practices. By this I am suggesting: - CVS repository be installed on a dedicated server rather than on a box contending with developers and other applications for memory, swap space and disk space - CVS repository be on a server where users don't have direct login access - shadowing of CVS repository in the event of a calamity for instant switchover to the other repository rather than wait for the lengthy restore process
Does anybody have any other suggestions, plus comments on the above? Thanks. Susan Johnson _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
