Re: best production practice?

[bobby temper]

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 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.

Now that means all our sites will have CVS folders, large updates will go 
throught cvs update, etc.

I would like to know if that's the best method of doing what i would like.

Best regards,
Bobby

> From: Rachel Burns <address@hidden>
> To: bobby temper <address@hidden>
> CC: address@hidden
> Subject: Re: best production practice?
> Date: Tue, 08 Feb 2005 19:17:36 -0800
>
> bobby temper wrote:
>
> > Hello CVS users,
> >
> > The company i work for is having difficulties keeping production and the 
> > repository in sync'.
> Not sure what you mean by production and repository in sync ?  Did you
> mean to say you want to have two repositories that need to be kept in sync 
> ?
> If yes you may want to look at http://www.wandisco.com/cvs for keeping
> multiple replicas in sync.
>
> > I would like to know, what is the best practice to achieve this? I'm 
> > thinking of having a cvs client on production, and having the production 
> > code being a checked out copy, with a cron job doing a cvs -n update, and 
> > emailing the results. But I am not sure thats the best way, as
>
>
> Looks like you want to determine what changed against a poduction 
> tag/branch ? If yes
> you might want to create a tag and diff against that.
>
> > other problems might occur with this solution. I would like to know if any 
> > of you have a better solution, or see the pitfalls in such solution.
> >
> > Thanks for your help,
> > Best regards,
> > Bobby
> >
> > _________________________________________________________________
> > Express yourself instantly with MSN Messenger! Download today - it's FREE! 
> > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> >
> >
> >
> > _______________________________________________
> > Info-cvs mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/info-cvs

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/