Comments on: Quickly Setup New Projects Using SVN http://www.thecrumb.com/2008/04/07/quickly-setup-new-projects-using-svn/ ColdFusion, Ant, jQuery and other geeky stuff with the occasional motorcycle post. Sun, 06 Jul 2008 02:33:34 +0000 http://wordpress.org/?v=2.5.1 By: Rob Wilkerson http://www.thecrumb.com/2008/04/07/quickly-setup-new-projects-using-svn/#comment-5244 Rob Wilkerson Mon, 07 Apr 2008 19:35:44 +0000 http://www.thecrumb.com/?p=409#comment-5244 I worked with my sys admin to do just that. The script creates the new environment, scripts out a new Trac project (with permissions set) and links the two. Quick and easy. Can't beat that, right? :-) I worked with my sys admin to do just that. The script creates the new environment, scripts out a new Trac project (with permissions set) and links the two. Quick and easy. Can’t beat that, right? :-)

]]> By: Jim http://www.thecrumb.com/2008/04/07/quickly-setup-new-projects-using-svn/#comment-5243 Jim Mon, 07 Apr 2008 19:31:49 +0000 http://www.thecrumb.com/?p=409#comment-5243 @Rob - Hopefully we're doing it the right way :) Your system sounds very similar - and much easier in your one repo/multi-project environment. At some point I need to build a little script so I can just go 'create projectname' and it'll run everything for me... @Rob - Hopefully we’re doing it the right way :)

Your system sounds very similar - and much easier in your one repo/multi-project environment. At some point I need to build a little script so I can just go ‘create projectname’ and it’ll run everything for me…

]]> By: Rob Wilkerson http://www.thecrumb.com/2008/04/07/quickly-setup-new-projects-using-svn/#comment-5242 Rob Wilkerson Mon, 07 Apr 2008 19:25:32 +0000 http://www.thecrumb.com/?p=409#comment-5242 It's always funny to read your posts about the same technologies I use. Seems our methods are almost always the same or nearly so. In my case I have one repository with multiple project directories. One of those projects is named ".template" (so that it appears at the top of any listing and to denote its status as a non-active- or hidden - project). When I need a new project, I just copy the contents of .template: svn cp -m "Copying base structure from the template" .template mynewproject I also keep a lot of core directories and files (e.g. build.xml.sample, _global.css) in my template. As long as I keep the template project up to date, any new projects will always get the latest. It's a very convenient system. It’s always funny to read your posts about the same technologies I use. Seems our methods are almost always the same or nearly so. In my case I have one repository with multiple project directories. One of those projects is named “.template” (so that it appears at the top of any listing and to denote its status as a non-active- or hidden - project). When I need a new project, I just copy the contents of .template:

svn cp -m “Copying base structure from the template” .template mynewproject

I also keep a lot of core directories and files (e.g. build.xml.sample, _global.css) in my template. As long as I keep the template project up to date, any new projects will always get the latest. It’s a very convenient system.

]]>