Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
> -----Original Message----- > From: Stasko, Roger [mailto:Roger.Stasko at LibertyMutual.com] > Sent: Thursday, July 03, 2003 12:38 PM > To: cvsnt at cvsnt.org > Subject: RE: [cvsnt] One Repository or Multiple Repositories > > > I recommend using multiple, customer-based repositories if your chosen > development tool supports them. > For example, Eclipse/WebSphere Studio Application Developer > allows each > project to have a different repository, so there's no penalty > for having > multiple repositories. Ah, but there is. Last time I checked, CVSNT was limited to 64 repositories. As our current active client list is at 104, keeping a repository for each one would simply not work. I highly recommend making a "Clients" repository and individual modules beneath that. As I understand it, the only limit on modules is the one imposed by the file system for folders. Likewise, as it takes an administrator to create a repository - do you really want a network admin in the chain of establishing a new client? This also allows you to maintain a single set of scripts for all the clients (for good or ill). > -----Original Message----- > From: David Williamson [mailto:dwilliamson at ivsi.com] > Sent: Thursday, July 03, 2003 2:18 PM > To: cvsnt at cvsnt.org > Subject: [cvsnt] One Repository or Multiple Repositories > > > To anyone who has an opinion, > > Our custom software shop is new to CVSNT and CVS in general. We are > debating the best approach to setting up our repository. Should we > setup a repository for each customer that we have and put > each of their > projects in a separate module or should we have one large software > repository that has a module for each customer? > > The administrators thought was to create a repository for > each customer > and place their projects within it. Reason: If something > happened to a > repository then our down time would be limited to one customer and > backup recovery would be easier by replacing the entire > repository from > last night's backup. > > The users thought was to create a single "Software" repository and > create a module for each customer and place their projects within it. > Reason: It would be easier to just go to the same repository and list > the modules. > > -- > > **************************************** > Name: David Williamson > Company: Integrated Visual Systems, Inc. > **************************************** > _______________________________________________ > cvsnt mailing list > cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt cvsnt downloads at march-hare.com https://www.march-hare.com/cvspro/en.asp#downcvs @CVSNT on Twitter CVSNT on Facebook > _______________________________________________ > cvsnt mailing list > cvsnt at cvsnt.org > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt >