if running on IIS/winxp u have a 1 site limit, but it's not so bad if as nathan says u make sure your sites work as sub directories as well as from the root which is easy to do simply by always using relative paths and/or mappings.
I set my sites up the same as they will be on the live server. e.g. d:\wwwroot\domainName\wwwroot and in IIS I make a virtual directory that points to the wwwroot of each site. So then at least the folde rnaming convention and file structure is the same as it will be on the live server. The only differene will be the lack of the vDir. Snake -----Original Message----- From: "Nathan Strutz" <[EMAIL PROTECTED]> To: CF-Talk <[email protected]> Date: Thu, 27 Apr 2006 14:35:43 -0700 Subject: Re: Subversion tips? > Matt, > > You've got the idea. Each developer shoudl be using the developer > edition of > CF. They usually connect to the central database server through their > own CF > copy. > > Working with multiple sites is more of a pain. With IIS, a developer > would > have to point their home folder to a different dev files working copy > folder, or set your various sites as subfolders and make sure the > coding is > clean enough to allow things like http://localhost/dopefly.com/. > > A great alternative is to use apache as the development web server, and > set > up multiple virtual sites, then you can screw with your hosts file so > dev.dopefly.com could point to a site running on my localhost. > > If you still like the 'central dev server' thing, which, btw, can > impose > licensing issues, then the way to go is give each developer a folder, > like > their own personal sandbox, then again mess with their host files or > your > internal DNS server so everything is easy for them. This way isn't as > cool > or safe because if one guy tries to run a risky recursion or a select * > from > * type query, everybody's hosed. > > In any event, your old dev site then becomes your staging server (cool, > eh?), good for testing and safely pushing controlled code to your > production > server. > > -nathan strutz > > > > On 4/27/06, Matt Williams <[EMAIL PROTECTED]> wrote: > > > > I'm looking to join the Real World and start using version control > > software. > > From what I've heard, SubVersion is as good as any. My environment is > > simple, but may not take full advantage of SubVersion. > > > > Windows 2003 server with IIS 6.0 > > CF 7 Professional > > 3 developers on 3 Windows XP workstations > > Mapped network drive to the development server > > Currentlly each developer just opens a file through the mapped drive, > does > > their edits, saves the file and uses IE/Firefox to browse to the page > for > > testing. > > > > I've started reading the svn-book, and so far understand everything. > The > > 'Working Copies' deal is what I'm most unclear on. Would each > developer > > need > > to run CF locally (developer version) so they can edit and test their > > 'Working Copy'? If not, how does my server (since I'm not on Apache) > know > > what version a given developer is working on? > > > > Any tips would be most appreciated. > > > > Matt > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:238989 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
