info-cvs
[Top][All Lists]
Advanced

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

Re: Web developpement with CVS...


From: Jim Ray
Subject: Re: Web developpement with CVS...
Date: Wed, 03 Oct 2001 16:18:11 -0600
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010913

address@hidden wrote:

Hi,
We are trying to install CVS on one of our server.  Right now, it's up
and running and works pretty fine.  It runs on a Linux box and we can
connect to it with WinCvs on our Win2000 workstations.

The problem is simple : we do web developpement, which means the
latest version of the files should always be present on the server,
not only in the cvs repository.

I would have them set it up in sandboxes.  If you are using Apache as the
web server this is simple to do with virtual hosts each pointing to a
different dir.  Or you could do it with just using public_html dirs that
are also samba export so they can get to them via Windows.  Checkout into
that dir and then they can edit.  With virtual domains they would be
able to check it before the commit.  That way you don't get seriously
broken code in CVS.

Hope all this makes some sense.

The syncing part is different I don't know if you want your web site syncing to head all the time. You may be better off syncing it to a tag like QA or something that way you know the code is good. Then write a little script to do the cvs update and put it in cron for every hour or something like that via ssh. This is probably not exactly technically correct but should get you in the ball
park for syncing.  You would need to set up keys for the user with ssh.

Something like this:

#/bin/sh

address@hidden:/path/to/cvsroot
CVS_RSH=ssh
WEBDIR=/path/to/htdocs
LOGFILE=update.log
DATE=`date +%m%d%h

# Move the logfile.

mv $LOGFILE $LOGFILE.$DATE
cd $WEBDIR

# Create a tag so you can roll back.

cvs rtag -r QA WEB_SITE_$DATE

# Update the site to the latest tag.

cvs update -r WEB_SITE_$DATE modulename >> update.log

# if you want to get fancy you could do a mail
# everytime it does this and attach the logfile.


jim



Let me explain myself :
Suppose we're working on a project with some PHP, I don't want to
install PHP on every programmer's workstations...  I'd like them to
simply checkout their stuff...do their changes..commit it and than
check (via their web browser) on the server to see if it's right...

What is the best way to do this ?  Is there any way to ask CVS to copy
the changed file at the right place, and this, at each commit ?  Since
we host sites both on Linux and Win2000, will cvs even be able to copy
the files over the network to another web server ?

Thanks a lot people... I hope this is not too stoopid :)

Regards,


Jonathan Kemp
Internet Services Manager
Capella Technologies
_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs







reply via email to

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