In the past I have actually gone as far as to setup an individual website and database for each developer (i.e. developername.dev.yoursite.com) which has its own webroot. Each user then maps the webroot. This solution works great for CF and VSS, and starteam should play fine with it!

- jason.

----- Original Message ----- From: "Adam London" {alondon@isisnewmedia.com> To: "CF-Server" <cf-server@houseoffusion.com> Sent: Thursday, January 25, 2001 9:23 PM Subject: Source code control with CF

> > We're planning to install a SCC system (StarTeam) in our shop, but are > hampered by the fact that the architecture SCC is not really compatible with > a server-side scripting environment like CF. The SCCS wants all users to > use a directory on their local machine as a working directory, and we don't > want to install CF Server, IIS and all the source code and GIFs on every > developers' workstation--and then pull our hair out trying to keep them in > synch. > > StarTeam will let you use a single shared folder on the server as a working > directory for everyone, but then it doesn't really control the files--you > can check things in and out of the SCCS, but it exert any control over what > people do on the folder. > > Ideally, we'd want to configure our SCCS so that it alone controls access to > the directory on the server where the source code lives--so that checking in > and out actually means something. > > Has anyone found a SCCS that works better with CF? Has anyone who has > worked with StarTeam for CF development found a better way to set it up? > > Adam London > Isis New Media > alondon@isisnewmedia.com > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm ------------------------------------------------------------------------------ To unsubscribe, send a message to cf-server-request@houseoffusion.com with 'unsubscribe' in the body or visit the list page at www.houseoffusion.com