[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Dev & Production repositories?

From: Kevin Old
Subject: Dev & Production repositories?
Date: 14 May 2003 00:25:40 -0400

Hello everyone,

I'm a CVS newbie, but learning fast.  I need some help with determining
the best way to go about setting up CVS for my project.

First, I have two physical servers (dev and production).  I'm currently
making changes to files on my dev server and then ftp'ing them to my
production server.  I need version control badly as files are getting
over written, etc.

I'd like to be able to checkout the dev module and make changes, then
test them (which if I understand correctly takes a commit before the
changes are uploaded to the repository) on the dev server, then if all
goes well, have the appropriate files committed to the production
server.  Keep in mind that there would be two repositories each on
different servers. I've seen the project CVSviaFTP, but don't want
things to be committed to production until it's been tested in dev and
explicitly flagged to be committed to production.  I've heard this setup
is complicated.

Another way I've heard about is to make a module on the production
repository, then create a branch for dev.  I could use the loginfo
script below to update stuff based on where it was checkedout.... 

^foundation     (date; cat; (sleep 1; cd /var/lib/interchange/foundation_dev; \
cvs -q up -d; cd /var/lib/interchange/foundation; cvs -q up -d) &) \
 >> $CVSROOT/CVSROOT/updatelog 2>&1
ALL     /usr/bin/cvs-log     $CVSROOT/CVSROOT/commitlog $USER "%{sVv}"

Maybe I'm just confused with it all.  I've read the documentation at
but haven't found a source that shows me how to layout my environment for Dev,
staging, production or dev/production.

Any help is appreciated!

Kevin Old <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]