Other Software

ID #69

Do you provide CVS?

Applies to: Grid System

Yes, the cvs command is available in your home directory to manage your own private cvs repository. CVS is available as soon as you signup for hosting and requires no special setup.

You can access your repository while logged into your local Modwest shell account using the cvs command.

To create a new cvs repository, type:

cvs -d /cvs init

If you have your own unix computer with ssh installed, you can also access your repository from there, using cvs over ssh. On your remote unix machine, set your CVS_RSH and CVSROOT environment variables:

export CVS_RSH=ssh
export CVSROOT=:ext:username@shell.modwest.com:/cvs

Then you can run cvs commands normally from your remote system like so:

cvs checkout blah

where "blah" is the name of a cvs project that you created.

You will be prompted for your password since the connection is over ssh. To avoid that, you could use ssh-keygen on your remote system.

This describes how to get cvs setup for use with your hosting account username. If you need multiple cvs users who all need to write to the same projects, please contact us.

If you are trying to connect to your CVS repository from a Windows machine (using WinCVS or a similar GUI app), http://www.ifm-services.com/people/jamesk/papers/cms/cvs-win32-client.html explains how to run cvs over ssh. You will need a command-line version of ssh for Windows, which is included with the Cygwin package.

If you want to avoid being prompted for your password when you connect, create ssh keys (as described in the CVSGuide page or in this FAQ). CVS does not use rhosts or passwd files.

There is no avoiding using ssh to connect to cvs, even if you are willing to accept the security risks. This is because without using ssh as a transport, cvs would have to run as a daemon and be setup for each individual user, which we don't want to do. Using ssh as the transport gives you security and removes the necessity of running cvs as a network daemon.

Finally, you do not need an SSL certificate to connect to cvs over ssh because ssh doesn't use SSL-style encryption.

Last update: 2010-09-29 16:35
Author: FAQ Admin
Revision: 1.2

Digg it! Share on Facebook Print this record Send FAQ to a friend Show this as PDF file
Please rate this FAQ:

Average rating: 3 (1 Vote)

completely useless 1 2 3 4 5 most valuable

You can comment this FAQ

Comment of Anonymous:
Make sure that there is a login created for you, or the SSHV2 won't work correctly.
Added at: 2003-06-09 12:27

Comment of Anonymous:
More instructions for Windows users are here:

Added at: 2004-02-01 20:27

Comment of Anonymous:
If you're using CVS to work on your website, you should make sure that a browser cannot request the contents of any CVS/ directories that may be under your DocumentRoot.

One way to do that is to turn off DirectoryIndexes in an .htaccess file:


Another way is to block access to the specific files inside the CVS dir in an .htaccess file (http://httpd.apache.org/docs/mod/core.html#files):

Order allow,deny
Deny from all

Added at: 2004-02-17 13:14

Comment of Anonymous:

- Download CVS spam from http://www.badgers-in-foil.co.uk/projects/cvsspam/
- Upload the file to your /cvs folder
- With the shell, decompress the tarball with tar -zxvf cvsspam???.tar.gz
- Rename the resulting folder "cvsspam"
- cd /cvs/CVSROOT
- chmod 777 commitinfo
- vi commitinfo, and add the line
ALL /usr/bin/ruby /cvs/cvsspam/record_lastdir.rb
- save the change
- chmod 444 commitinfo
- chmod 777 loginfo
- vi loginfo, and add the line
ALL /usr/bin/ruby /cvs/cvsspam/collect_diffs.rb --to me@mydomain.com %{sVv}
- save the loginfo
- chmod 444 loginfo
- make the directory /etc/cvsspam/
- mv /cvs/cvsspam/cvsspam.conf /etc/cvsspam
- ModWest's sendmail does not accept the -oi option (see http://www.modwest.com/help/kb10-124.html) used by cvsspam. Remove the option from /cvs/cvsspam/cvsspam.rb
- To add more people to the send list, check the /etc/cvsspam/cvsspam.conf file
Added at: 2005-11-10 03:50