Don't put words into my mouth. As for xml changes that are not related to your source code is generally handled by daily backups anyway, and most people prefer that as it can put the machine into a state quicker than your method. But hey thats your choice, you want to create extra work for you then go for it.
As for the actual content of the source files, DID I EVER MENTION ANYTHING about that? NO, I did not and I wouldn't like to have you tell me otherwise. -- Senior Coldfusion Developer Aegeon Pty. Ltd. www.aegeon.com.au Phone: +613 9015 8628 Mobile: 0404 998 273 -----Original Message----- From: Jochem van Dieten [mailto:[EMAIL PROTECTED] Sent: Monday, 11 August 2008 10:23 PM To: CF-Talk Subject: Re: SVN in Production Andrew Scott wrote: > What > Do you mean by repo -> server and server -> repo? > > The latter should never be an issue, or even considered. Anyone who makes > changes to production and not in a development environment shouod be hung > out to dry or better still beaten with a stick until you realise that > development is what it means. So you think the entire /etc/ folder on a production box is the same as an /etc/ folder on a development box? You think they have the same hostnames? The same IP addresses? The same firewall rules? That the test environment has a two year backup retention like production has? Not everybody uses SVN just for sourcecode. Some use it for their university thesis. Some for their grocery list. Some use SVN for complete server configurations. And what you use it for does influence the usage pattern. It is perfectly acceptable to change the -Dmail.host oarameter in your jvm.config file directly on production and then back it up to SVN. > Once you have deployed to a production server, it should never have any ties > with the repository in any way shape or form. If you are one of those that > think this is ok, then you will need to adopt new procedures quickly. Before > you adopt bad and I mean VERY BAD ideas. Generally speaking you don't want to have production running directly from a working copy. But there is nothing wrong with putting $Id$, $HeadURL$ etc. in your sources so that code and configuration files on the production box points back to a specific version of a file in a repository. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:310787 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
