Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
First off, make it policy that all changes are committed before nightly backups run. Any data loss responsibility falls on the person who was not following policy. Keep the sandboxes on the local machines and DO NOT back them up. Use a client like TortoiseCVS to easily show files that need to be committed. Second, with the servers running on the local machines, you won't necessarily need to maintain DNS entries. Suppose you distribute a hosts file that indicates "my-client1 127.0.0.1, my-client2 127.0.0.1", or (I'm not sure if this is possible) convince your DNS server to return 127.0.0.1 mapping for any of the "my-clientx" requests. This assumes that you actually need to view the different "sites" as independent. Can the live as sub-folders on the local web server for developing purposes? Another approach may be to have an often "CVS Updated" development server. This is similar to how we occasionally work here. With 5 programmers on a project (we work with A/V control systems), each fixing his own issue and confirming that his code will compile, committing the code, then we nominate someone to do a "UCDR" (Update, Compile, Download (to the system), Reboot (the system) ) to get everyone's changes into the running system. Now, since you don't have to compile ASP (unless something's changed since I worked on it last), a simple update on the development server should suffice. This can be scripted so anyone can do it for any project at any time to test out their code changes. Once everyone is content with the code running on the dev server, update the live servers (which is now running out of its own sandbox). Hows that sound? I'll bill you later ;-) __________ I should have known better than to trust the logic of a half-sized thermocapsulary dehousing assister... > -----Original Message----- > From: Drew McLellan [mailto:dru at dreamweaverfever.com] > Sent: Tuesday, March 18, 2003 12:22 PM > To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > Subject: [cvsnt] Workflow advice saught > > > I've managed to get the CVSNT server up and running on a Windows 2000 > server. > > As I understand it, the normal scenario with CVS is to have a central > repository, out of which developers check files, edit them on > their own > machines, and check them back in. This gets more complex when you're > working with web technologies, as the files need to be > accessible by a > web server at edit time. This means that each developer needs > to have a > local web server running when editing/testing files prior to > committing > them back to the repository. > > All fine so far, but consider this: > > My team are developing web applications in ASP. Every application > consists of at least two and sometimes three websites. The > files (even > checked out files) have to be stored on a server rather than a > workstation in order to get backed up each night. > > So this rules out using IIS on the workstations, as unless you are > running Win2k Server you are restricted to one site per > machine (and 10 > connections) we need 2 or 3 sites per ongoing project. We're going to > have to be checking files out into folders on a server instead of the > workstations, which is fine. > > I think this is the bit that's bothering me ... for every site in every > project for every developer I need to have: > > a) an IIS website > b) a DNS record to access the site > c) a 'working' folder on a server somewhere for files. > > Now say that there are 3 sites for one project and a > developer has two > projects on the go, that's 6 websites just for that developer. For a > team of 5, that's 30 websites, 30 DNS entries and 30 working folders. > > Which means I need: > > d) a server admin to look after it all. > > Unless I'm missing a better way of working. Any suggestions? > > drew > > _______________________________________________ > cvsnt mailing list > cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs >