Re: best production practice?

[Bill Moseley]

On Wed, Feb 09, 2005 at 03:52:29PM +, bobby temper wrote:
 Hello,
 
 What i meant is that, we have the code running on a production machine. Now 
 and then, that code gets changed, and sometimes, it's content gets out of 
 sync with whats on production (ie. for example. someone edit directly on 
 production, for a hotfix (i know this is bad, but fast for changing a 
 simple text, link, etc...) and forget to do the changes in cvs.

I would cvs checkout to a staging server and then make a package to
install on the production server, such as rpm or deb.  That allows you
to give your production releases version numbers.

I've also used tagged cvs check outs to mark releases.  And also just
simply cvs for simple sites.  But being structured with packaged
releases is nice.

 I would like a way to know when the code on production isn't the same as 
 the one in the source control (not to update production, but to update the 
 repository). So far, the best  way i thought of doing this was to have a 
 cvs client on the production servers, and periodically (cron job) do a cvs 
 -n update, logging the results.

That's to check for changes on the production server?

-- 
Bill Moseley
[EMAIL PROTECTED]



___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs

Re: Testing for updated files

[Bill Moseley]

On Mon, Feb 07, 2005 at 11:18:26AM -0800, [EMAIL PROTECTED] wrote:
 grep for  leading 'U' in cvs output.  In the form of :
 
 U path/to/my.file

Ah, that's easy.  Thanks.

cvs also writes this to stderr:

cvs server: Updating .
cvs server: Updating bin
cvs server: Updating lib

Can that be suppressed?  I'd like my cron job to be quiet unless
there's a problem and then mail me stderr output.

I guess the solution is to capture stderr and then if cvs returns
non-zero exit status cat that file and let cron mail it to me.

 Also, it may be better to add watches and watch actions to
 the cvs server.  You could have the watch post changed file name to a
 log and have your crontab check that file for changes.

This is cvs on SourceForge.  Not sure how much I can modify there.
But I'll take a look.

Thanks for the help!



-- 
Bill Moseley
[EMAIL PROTECTED]



___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs