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.
All, I appreciate all help and suggestions...However, the question and decision to prohibit IIS from running on developer machines is _well_ out of my reach. I'm sure I could circumvent whatever steps have been put in place to prevent me from utilizing IIS locally - however that simply is not a viable option for me. In any case, I'd like to make sure I have a clear understanding of the suggestions that have been made thus far, barring the switch to some other web server/framework/etc. - Create a sandbox/module on the network on the machine running CVSNT server - Install a plug-in or run a script that updates the web server directory (diff physical box) when a commit is made to the sandbox/module on the CVSNT server Please forgive my ignorance here, I've got no real experience administering source control environments until now. Lastly - As of now, if I create a module on the CVSNT server from TCVS on my local machine...if someone else goes to check it out, there are prompted for my password (we are utilizing SSPI) Is there a way to grant multiple users access to a module/repository/etc [while still utilizing SSPI]? Do we need to create the module with some generic account/group so that we all have access? If so - wouldn't we lose the accountability (ie, who committed what version) Sorry about all the questions! -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of John Peacock Sent: Wednesday, January 25, 2006 10:29 AM To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: [cvsnt] Re: CVSNT + Web Application Implementation Sanjay.Uttam at VerizonWireless.com wrote: > I've installed CVSNT + TortoiseCVS here...We develop 99% web applications. > THe issue is, our security policy prohibits us from running IIS on our > local(developer machines) Thus, I'm not sure exactly how to implement this > solution. Our code resides on network shares, and I have read in tons of > places that you should not create a respository on a network share. We do this (though not with IIS) through the use of a secondary test web server on the same box as the CVSNT repository (NOT VIA A NETWORK SHARE). Run a postcommit hook as described here: http://www.cvsnt.org/wiki/PostCommit?highlight=%28postcommit%29 so that the test web server gets updated each time a file is committed to the repository from the developer machines. The production web server is updated manually at discrete intervals (ideally after testing has been performed). ;-) HTH John _______________________________________________ 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 ___________________________________________________________________ The information contained in this message and any attachment may be proprietary, confidential, and privileged or subject to the work product doctrine and thus protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to this message and deleting it and all copies and backups thereof. Thank you.