1 rizwank 1.1 %META:TOPICINFO{author="RizwanKassim" date="1105856229" format="1.0" version="1.1"}%
 2             %META:TOPICPARENT{name="WebHome"}%
 3             In a fit of geekhood, I went ahead and setup a central CVS server for the lot of us to use. 
 4             This way we can share our demo code, enhancements and anything we run into (via CVS and the Wiki)
 5             
 6             So, for the moment, ignore the TA's statements on how to setup CVS on your ugrad account.
 7             
 8             	* Step 1 : Download [[http://www.geekymedia.com/cs103cvs.key cs103cvs.key]] and [[http://www.geekymedia.com/config config]] to your development system.
 9             	* Step 2 : Copy those files into your ~/.ssh directory. (the .ssh directory in your home directory). If you have a previous config file, combine them.
10             	* Step 3 : Put the following statements into your startup script (usually .bashrc): 
11             		* export CVSROOT=:ext:rizwank@67.18.44.234:/home/rizwank/cvs
12             		* export CVS_RSH=ssh
13             		* obv, if you're using cshrc, your'd modify the syntax as needed
14             	* Step 4 : Enjoy!
15             		* Now, all you have to do (once you've restarted your shell to get the new stuff that you put into your script) is write _cvs <command> <package>_ to import, commit, update your cvs packages!
16             
17             How I set it up (with reasonable security) (for reference) : SetupCVSviaSSH
18             
19             
20             
21             For Reference:
22 rizwank 1.1 
23             Other stuff I found:
24             http://tony.aiu.to/sa/cvs/
25             
26             http://www.pizzashack.org/rssh/index.shtml
27             
28             b) You could provide a restricted shell on the cvs machine which only
29             	provides for the running of the 'cvs server' command and any commands
30             	that you need to run in your commitinfo/verifyinfo/loginfo/taginfo
31             	scripts. Many different kinds of restricted shells exist, which one
32             	you choose will depend almost entirely on your environment and goals.
33             
34             c) By forcing the /etc/ssh/rc to exec the '/usr/bin/cvs server' command
35             	for the user after always making usre the $HOME/.ssh/rc script is
36             	never allowed to exist... not really a very secure answer, but I have
37             	heard of folks using this appraoch...
38             
39             # $Id: WineCVS.txt,v 1.1 2005/01/16 06:17:09 RizwanKassim Exp rizwank $
40             
41             
42             
43 rizwank 1.1 -- Main.RizwanKassim - 16 Jan 2005
44