Models for Version Management of Web-Based Projects
We have several projects under config control using Merant's VM. Our new VM model is to group code by type (ex. C, Java, PL/SQL, etc.), because we have several (about 7) applications that use various types of code. This makes it easier for developers to transition between applications and easily identify the location of their source code in VM.
I now have a puzzling dilemma. We have a new web-based application that has files of the same name (like index.htm or submit.cgi). I can't create a VM subfolder under code called htm or cgi, because the VM folder will not allow files of duplicate names. The alternative is to create the entire application directory structure, even though many, many, many of these subdirectories have no 'code' files. I also can't see creating 30 sub-folders under cgi just so I can store these unique (but same named) files.
Does anyone out there have a VM (or any source control tool) model for web-based applications? All input is much appreciated! [img]images/icons/wink.gif[/img]
Re: Models for Version Management of Web-Based Projects
Okay then... Let's try this. If you had to deal with this, what would you do? It doesn't even have to be something with which you're experienced! I know you all have some great ideas, and no advice is bad advice!