Kym, I was not responding to you directly, if I did not answer your question then let me ask you this.
If you are tight for HD space, and not everyone is. But what good would it be too actually have .svn files on your production server? If it doesn't need to be required to run, then it doesn't need to be there. >From a security point of view, unless it is behind a VPN that is totally secure you have your code base open to the whole world when and if it is hacked. Small chance that someone would work out that your production server is connected to your SVN server. If you are like ME and most others, your company or business is behind a firewall. This means a number of things, and if hacked then the code could include your SVN details to connect to your SVN server. Unlikely, but why take the chance? Do you really want me to go further? SVN might be used by some people in production, and these people are in need of a good damn slapping and told to give it up... And over time, all changes made to production and stored back into .svn directories end up increasing your HD space so over a year it will grwo depending on how often youu make changes directly to production and DO NOT FOLLOW a full SDLC. But I guess that anyone who does use an approach of production->svn, do not know what an SDLC is all about or how to protect themselves. In one application, I had made changes to the application that DOES and WILL effect LIVE data. So until the client is happy it gores through the stages of dev -> QA -> production and then at least, once made live if the changes made to production effect live application data the ownus falls onto the developer and the client. If it is the developer, then they migrated changes that should never have been made live. If it is the client then they have no excuse, because it went through a QA phase for the client to approve from a UAT point of view... And I will make the assumption that if you follow an SDLC you would also be using the UAT, before a client signs of on the changes. Oh wait, some comments here have made a reference to the fact that changes are not signed off on. Which means you could have 20 changes waiting for approval, how do you migrate these changes? You certainly would not export the entire repository now would you? -- Senior Coldfusion Developer Aegeon Pty. Ltd. www.aegeon.com.au Phone: +613 9015 8628 Mobile: 0404 998 273 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:310698 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
