You could manage access control just as easy using one repository (one
group pr. module, with full access) - but why let anybody have access to
the repository? Only cvs should have this access (and the guy who have to
administer cvs)
Regards
J�rgen M�ller Larsen - Nykredit Data - Koncernmetode og Arkitektur (KMF-V)
- Telefon: +45 9635 5069 - email: [EMAIL PROTECTED]
"Anders
Truelsen" Til: <[EMAIL PROTECTED]>
<at@systematic cc:
.dk> Vedr.: RE: [Cvsnt] How many repositoreis can
CvsNt server typically
Sendt af: handle
cvsnt-admin@cv
snt.org
2002-05-23
10:25
Besvar
venligst til
"Anders
Truelsen"
Hi Bo
We have a couple of large projects that has there own cvs servers, and a
couple of locales that has local servers, but the rest of us share a
server.
The main advantage of separate repositories is that access control is
easier that way, one group pr. repository, with full access.
Regards,
anders
-----Original Message-----
From: Bo Berglund [mailto:[EMAIL PROTECTED]]
Sent: 23. maj 2002 09:17
To: Anders Truelsen
Cc: CVS-NT Mailing list (E-mail)
Subject: RE: [Cvsnt] How many repositoreis can CvsNt server typically
handle
Anders,
why do you run a separate repository for each project?
This is not the standard way as I have read the CVS usage docs.
After a while you will get past the 64 limit and then what?
Storing each project as a module in a single repository or didviding
them among a limited set of repositories each handling a class of
projects (say customer based or similar) makes more sense to me.
But you may have a special setup of course....
/Bo
-----Original Message-----
From: Anders Truelsen [mailto:[EMAIL PROTECTED]]
Sent: den 23 maj 2002 08:07
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [Cvsnt] How many repositoreis can CvsNt server typically
handle
Hi Bo
We're currently hosting about 30 repositories (one for each active
project in the house) on our CVS server, so the for me the question
makes perfectly go sense as stated :-)
Regards
/anders
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 23. maj 2002 08:00
To: [EMAIL PROTECTED]
Subject: Re: [Cvsnt] How many repositoreis can CvsNt server typically
handle
On Thu, 23 May 2002 04:06:39 +0000 (UTC), Arvind Raman
<[EMAIL PROTECTED]> wrote:
>We have currently transitioning to cvs, and our setup
>includes the WinCvs client and the CvsNT server. We
>are using the "ntserver" protocol for authentication.
>I just thought it might be worthwhile to ask if there
>is a limitation on the number of repositoreis the
>CvsNT server could support.
>Do we have to keep a tab on the number of repositories
>?
>
>Thanks and regards
>Arvind
>
>
To answer your question as asked:
Max number of repositories for CVSNT == 64
But also:
I suspect that your question comes from a misconception that I have
seen a number of times. People tend to confuse repositories and
modules.
Repositories are the separate storage areas for modules, in theory
(and many times in practice) a CVS server could work well with only
one repository.
Modules are the actual 'projects' that are checked in to the CVS
server. Each module is separately stored in a repository and contains
all files and folders needed for a project. There is no limit to the
number of modules that can be handled (except disk space and such).
/Bo
(Bo Berglund, developer in Sweden)
_______________________________________________
Cvsnt mailing list
[EMAIL PROTECTED]
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
_______________________________________________
Cvsnt mailing list
[EMAIL PROTECTED]
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
_______________________________________________
Cvsnt mailing list
[EMAIL PROTECTED]
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
_______________________________________________
Cvsnt mailing list
[EMAIL PROTECTED]
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
