Tag! On my team of about 10 developers, 4 of us have stepped out of the dark ages and are using CVS, actually only 2 of us use it fully, the other 2 are forced into it :) We use CVSNT also along with Tortoise. At the moment I manually export and copy to the 'staging' and production environments. Just use cvs export from the cmd prompt using the -d switch to specify a directory other then the module name.
example: cvs export -DNow -R -dsome/relativeorabsolute/path/to/your/directory modulename Then copy from this directory to the actual one overwriting files. You could write a batch file to do this or even a CF script. IIRC, tortoise allows you to export to a named directory also. Checkout tortoise at tortoise.org<http://tortoise.org>, its da bomb. peas DK On 5/1/05, Joerg Zimmer <[EMAIL PROTECTED]> wrote: > > >Hmm, I thought I'd blogged a fair bit about it over the years... Maybe > >not. Can you be a bit more specific about what you'd like to see? > >-- > >Sean A Corfield -- http://corfield.org/ > >Team Fusebox -- http://fusebox.org/ > > Hi all, hi Sean, > as some kind of newbie to your blog (reading for about two months), I'd > really like to read about this! > > Version control is a big topic in my company at the moment. > Till the beginning of the year we worked with 2-4 developers on one > dev-machine. > Each developer on his own project. > Finished projects were then deployed to the productive server. > > With enlarging projects, requiring more than one developer working on it, > we thougt about version control. > After reading a lot of pages about versioning in > web-development-environments, we changed our structure to a productive > server, a staging server (the old dev-machine), which is additionally > hosting the CVSNT server and Sandbox-Workstations which got an IIS and a > local CFServer. > > As CFStudio has no satisfying handling for CVS, we simultaneously switched > to CFEclipse. It's quite cool, even though we're missing some features / > have to abandon some old habits. But it's really worth a try!!! > > What still isn't totally clear to us is the process of handling the > staging and production versions. Actually we're just file-copying the > checked-out versions on our workstations to the servers... not the right > approach anyway... > (Exporting to the Server directly from CVS brings conflicts about files > being in the way... No need to mention that we don't want to delete the > files on the production-server before we check out the up-to-date > version...) > But I still haven't found a good documentation about this. > > If anyone has a tip or if that could be part of your blog-posting Sean, it > would be great! > > Greetz from Germany > > Joerg > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:205200 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
