(cvs.info.gz) Remote repositories

 
 2.9 Remote repositories
 =======================
 
 Your working copy of the sources can be on a different machine than the
 repository.  Using CVS in this manner is known as "client/server"
 operation.  You run CVS on a machine which can mount your working
 directory, known as the "client", and tell it to communicate to a
 machine which can mount the repository, known as the "server".
 Generally, using a remote repository is just like using a local one,
 except that the format of the repository name is:
 
      [:METHOD:][[USER][:PASSWORD]@]HOSTNAME[:[PORT]]/path/to/repository
 
    Specifying a password in the repository name is not recommended
 during checkout, since this will cause CVS to store a cleartext copy of
 the password in each created directory.  `cvs login' first instead
 ( Password authentication client).
 
    The details of exactly what needs to be set up depend on how you are
 connecting to the server.

 
* Server requirements         Memory and other resources for servers
* The connection method       Connection methods and method options
* Connecting via rsh          Using the `rsh' program to connect
* Password authenticated      Direct connections using passwords
* GSSAPI authenticated        Direct connections using GSSAPI
* Kerberos authenticated      Direct connections with Kerberos
* Connecting via fork         Using a forked `cvs server' to connect
* Write proxies               Distributing load across several CVS servers

Info Catalog

(cvs.info.gz) Moving a repository

(cvs.info.gz) Repository

(cvs.info.gz) Read-only access

automatically generated byinfo2html

(cvs.info.gz) Remote repositories

Menu