[ciapug] Subversion for Web Dev SCM

[Chris Van Cleve]

Yes, not just any minions... tasty ones...

Chris VC

On Mar 8, 2006, at 10:16 AM, Barry Von Ahsen wrote:

> Vanish has minions?
>
> </bad buffy ref>
>
> -barry
>
>
> Chris Van Cleve wrote:
>> Yes, I have a three tiered environment.
>> All developers have access to the trunk, and can export to the  
>> development web area for testing.
>> 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.
>> 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
>> Chris VC
>> On Mar 8, 2006, at 8:51 AM, <Daniel.Juliano at wellsfargo.com>  
>> <Daniel.Juliano at wellsfargo.com> wrote:
>>> If I read your question properly, this sounds like a three  
>>> environment system issue.
>>>
>>> In a perfect-for-deployment world, you would want to have a  
>>> scripts that run for:
>>> 1) check out to development environment (typically, developers  
>>> machines)
>>> 2) check out to test environment (hopefully a box that developers  
>>> have restricted access to)
>>> 3) check out to production environment (hopefully a box that  
>>> developers have no access to whatsoever)
>>>
>>> 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.
>>> Daniel Juliano
>>>
>>>
>>> From: ciapug-bounces at cialug.org [mailto:ciapug- 
>>> bounces at cialug.org] On Behalf Of Tim Champion
>>> Sent: Tuesday, March 07, 2006 4:02 PM
>>> To: ciapug at cialug.org
>>> Subject: Re: [ciapug] Subversion for Web Dev SCM
>>>
>>> My current employer uses svn successfully, although I'm far from  
>>> an expert on svn :)
>>> 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.
>>>
>>> On 3/7/06, Chris Van Cleve <vanish at dreamscapevisionery.com> wrote:
>>> IS anyone out there successfully using Subversion for SCM on their
>>> web development projects? I'm having a bear of time getting my head
>>> around making it work. I have svn installed and working properly. No
>>> problems there, both server and client. Here's my conundrum:
>>>
>>> I have my code in a repository and all of the developers can access
>>> it through svn just fine. Checkin, checkout, etc. What I can't make
>>> work is having the dev code running in a sub-domain. Do I need to
>>> export the trunk to a web-enabled directory? I need the SCM only for
>>> preventing code loss and overwrites between developers. I can't  
>>> point
>>> Apache to the repository because, well, the files aren't really
>>> there... and running a live web instance on your trunk code just
>>> sounds like an idea firmly lodged in the 'bad' category to me.
>>>
>>> Any help greatly appreciated.
>>>
>>> Chris VC
>>> _______________________________________________
>>> ciapug mailing list
>>> ciapug at cialug.org
>>> http://cialug.org/mailman/listinfo/ciapug
>>>
>>>
>>>
>>> --Tim Champion
>>> timchampion at bigfoot.com
>>> _______________________________________________
>>> ciapug mailing list
>>> ciapug at cialug.org
>>> http://cialug.org/mailman/listinfo/ciapug
>> --------------------------------------------------------------------- 
>> ---
>> _______________________________________________
>> ciapug mailing list
>> ciapug at cialug.org
>> http://cialug.org/mailman/listinfo/ciapug
>
>
> _______________________________________________
> ciapug mailing list
> ciapug at cialug.org
> http://cialug.org/mailman/listinfo/ciapug
>
>