[Top][All Lists]

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

Re: best production practice?

From: Bill Moseley
Subject: Re: best production practice?
Date: Wed, 9 Feb 2005 09:05:28 -0800
User-agent: Mutt/1.5.6+20040907i

On Wed, Feb 09, 2005 at 03:52:29PM +0000, 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

reply via email to

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