<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">Yes, I have a three tiered environment.<DIV><BR class="khtml-block-placeholder"></DIV><DIV>All developers have access to the trunk, and can export to the development web area for testing.</DIV><DIV>Only I have access to the Staging and Production web areas. I chose to export instead of checkout to the web areas to reduce unnecessary clutter with .svn files and directories in the web tree.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Unfortunately it looks like my only option for managing the include files is with a separate repository. Makes the mental management for developers a bit thicker but I think we can all handle it. Hell, I'm just happy I'm not the sole web developer anymore. I have lackeys to dump the monotonous coding on. ;D</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Chris VC</DIV><DIV><BR><DIV><DIV>On Mar 8, 2006, at 8:51 AM, <<A href="mailto:Daniel.Juliano@wellsfargo.com">Daniel.Juliano@wellsfargo.com</A>> <<A href="mailto:Daniel.Juliano@wellsfargo.com">Daniel.Juliano@wellsfargo.com</A>> wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"> <DIV dir="ltr" align="left"><FONT face="Verdana" size="2"><SPAN class="561424514-08032006">If I read your question properly, this sounds like a three environment system issue.</SPAN></FONT></DIV> <DIV dir="ltr" align="left"><FONT face="Verdana" size="2"><SPAN class="561424514-08032006"></SPAN></FONT> </DIV> <DIV dir="ltr" align="left"><FONT face="Verdana" size="2"><SPAN class="561424514-08032006">In a perfect-for-deployment world, you would want to have a scripts that run for:</SPAN></FONT></DIV> <DIV dir="ltr" align="left"><FONT face="Verdana" size="2"><SPAN class="561424514-08032006">1) check out to development environment (typically, developers machines)</SPAN></FONT></DIV> <DIV dir="ltr" align="left"><FONT face="Verdana" size="2"><SPAN class="561424514-08032006">2) check out to test environment (hopefully a box that developers have restricted access to)</SPAN></FONT></DIV> <DIV dir="ltr" align="left"><FONT face="Verdana" size="2"><SPAN class="561424514-08032006">3) check out to production environment (hopefully a box that developers have no access to whatsoever)</SPAN></FONT></DIV> <DIV><FONT face="Verdana" size="2"></FONT> </DIV> <DIV><SPAN class="561424514-08032006"><FONT face="Verdana" size="2">The test and production scripts should be handed a version number to check out, which allows you to 'certify' a particular build number as production-ready. There may be a multi-week gap between deploy to test and deploy to production, and your developers can continue checking in changes against the trunk without impacting your deployments.</FONT></SPAN></DIV><P><SPAN lang="en-us"><FONT face="Verdana" size="2">Daniel Juliano</FONT></SPAN><BR></P><BR> <DIV class="OutlookMessageHeader" lang="en-us" dir="ltr" align="left"> <HR tabindex="-1"> <FONT face="Tahoma" size="2"><B>From:</B> ciapug-bounces@cialug.org [<A href="mailto:ciapug-bounces@cialug.org">mailto:ciapug-bounces@cialug.org</A>] <B>On Behalf Of </B>Tim Champion<BR><B>Sent:</B> Tuesday, March 07, 2006 4:02 PM<BR><B>To:</B> <A href="mailto:ciapug@cialug.org">ciapug@cialug.org</A><BR><B>Subject:</B> Re: [ciapug] Subversion for Web Dev SCM<BR></FONT><BR></DIV> <DIV></DIV>My current employer uses svn successfully, although I'm far from an expert on svn :)<BR>What we do here, is have each developer checkout their development branch onto their local machine (which is a LAMP box). I think you answered your own question, and you would have to checkout the trunk or a devel branch (or whatever you want to test) to a test web server, or to the subdomain's DocumentRoot of your SVN server if that's where you want it to run.<BR><BR> <DIV><SPAN class="gmail_quote">On 3/7/06, <B class="gmail_sendername">Chris Van Cleve</B> <<A href="mailto:vanish@dreamscapevisionery.com">vanish@dreamscapevisionery.com</A>> wrote:</SPAN> <BLOCKQUOTE class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">IS anyone out there successfully using Subversion for SCM on their<BR>web development projects? I'm having a bear of time getting my head<BR>around making it work. I have svn installed and working properly. No<BR>problems there, both server and client. Here's my conundrum: <BR><BR>I have my code in a repository and all of the developers can access<BR>it through svn just fine. Checkin, checkout, etc. What I can't make<BR>work is having the dev code running in a sub-domain. Do I need to<BR>export the trunk to a web-enabled directory? I need the SCM only for <BR>preventing code loss and overwrites between developers. I can't point<BR>Apache to the repository because, well, the files aren't really<BR>there... and running a live web instance on your trunk code just<BR>sounds like an idea firmly lodged in the 'bad' category to me. <BR><BR>Any help greatly appreciated.<BR><BR>Chris VC<BR>_______________________________________________<BR>ciapug mailing list<BR><A href="mailto:ciapug@cialug.org">ciapug@cialug.org</A><BR><A href="http://cialug.org/mailman/listinfo/ciapug">http://cialug.org/mailman/listinfo/ciapug</A><BR></BLOCKQUOTE></DIV><BR><BR clear="all"><BR>-- <BR>Tim Champion<BR><A href="mailto:timchampion@bigfoot.com">timchampion@bigfoot.com</A><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">ciapug mailing list</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:ciapug@cialug.org">ciapug@cialug.org</A></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="http://cialug.org/mailman/listinfo/ciapug">http://cialug.org/mailman/listinfo/ciapug</A></DIV> </BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>