|
|
CVS Server from scratch, step-by-step ...
hi all,
i've been wanting to setup a a remote/central cvs server for Web Development versioning for awhile. the previous comments here on MacOSXHints were, as usual, helpful (thanks!) for using OSX's bundled cvs. wanting to get all my cvs clients & servers to a single, recent version with a reproducible proces, I set out to build/configure cvs server from scratch ... and spent some time collecting the info i'd found given some of the questions/comments i've read, i hope some'll find this step-by-step helpful! cheers, richard cvs-1.11.9(CVS Home Page) (login as root ...)
DOWNLOAD:
cvs-1.11.9.tar.bz2
Change these configure options as required; in particular note: your approrpiate choice of:
CREATE/INITIALIZE the repository
I assume here a root directory for the cvs repository of "/usr/local/cvsrep" This can, of course, be any directory you wwant -- just make sure you have enough free drive space !
Checkout the CVSROOT configuration/info files to, e.g., your Desktop:
You should see the following output:
We're going to make some changes to the checked-out files.
note: don't edit files IN the repository!
Restrict cvs access to just yourself ...
CREATE a new file:
and ADD a line(s) for your authorized user(s):
ADD "writers" to your CVSROOT check-out list
Commit both changed files, adding a first comment
Setup network access to CVS's pserver in NetINfo
Setup pserver for control by inetd
ADDing the following line ...
Note:
I suppose you can make like changes in xinetd as well ... I'm not certain of the value of choosing inetd vs. xinetd, since both are called by /System/Library/StartupItems/IPServices/IPServices Reload inetd's settings (comments anyone?)
Now you're ready to IMPORT & use your production directory
assuming your "target"" directory is "/Library/WebServer/Documents" on the same machine, and your source module name will be "web_production" ...
you should now see your newly created "web_production" project as a folder
in your cvs root, i.e.: "/usr/local/cvsrep/web_production" for sanity's sake, move your EXISTING files temporarily out of the way
and CHECKOUT/push your repository's tree for your production files
or, from any other machine via, e.g., ssh, to any location with an installed cvs client
Now Checkout, Commit, Fold, Spindle & Mutilate to your hearts' content ...
CVS Server from scratch, step-by-step ...
> % kill -HUP `ps cax | grep inetd | awk '{ print $1 }'` |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.33 seconds |
|