You could, but as mentioned, this would make administration harder, and it doesn't make sense creating separate repositories for a 3 file project.
What needs to be understood, however, that a repository revision number is not very meaningful, other then, it's a state of the repository at a certain point in time. There are a lot of discussions about this on the svn-users list, because a lot of people coming from CVS are used to their being version numbers for each file. Russ > -----Original Message----- > From: Eric Roberts [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 01, 2007 11:01 PM > To: CF-Talk > Subject: RE: Daily procedures for using Subversion > > You could also put each project in a separate repository. If you do this, > they will all have their own version numbers. > > Eric > > -----Original Message----- > From: Richard Kroll [mailto:[EMAIL PROTECTED] > Sent: Thursday, 01 February 2007 08:19 > To: CF-Talk > Subject: RE: Daily procedures for using Subversion > > You said that you thought of putting the entire web root under source > control. Is the web root one project, or do you have multiple > applications > running under it? If it is one project then can create a repository where > the trunk would be your entire web root. The repository structure would > look like: > > |- Repository root > |-trunk > |-tags > |-branches > > The problem with this approach is what happens if a new application needs > to > be put under source control? You end up with a very strange repo tree. > I suggest creating your repository like: > > |-Repository root > |-app1 > |-trunk > |-etc. > |-app2 > |-trunk > |-etc. > > I would not worry too much about the revision numbers and how they > increment > with each committed change. They are there to enable you to isolate each > atomic commit that took place. In terms of deployment and matching how > you > currently work, you could simple have your production server be a > 'check-out' of the appropriate repository. You could also integrate ANT > into your process and have build scripts automatically deploy your > application. > > >Also, how often do you > > commit a change to the repo? And last, how do you work when you need > to > > get something out of the repo to work with? Do you download it to > your > > local machine, or download to a test server? > > You can simply check-out a projects trunk into a local folder. When > changes > were needed, you would update your local environment (SVN Update), do the > work needed, test, and then commit your changes. > > Suggested best practice is to create a tag or branch when you are ready to > deploy, and simply deploy that tag/branch to your production servers. > > > HTH, > > Rich Kroll > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:268523 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
