Heh, not really.  I thought this stuff was common to most places where
versioning and development and controlled deployments go
hand-in-hand-in-hand.

I have put together a short preso for SVN noobs at my local WordPress
user group meeting next month.  Something about teaching SVN to people
who have never seen it is fascinating to me.  I love witnessing that
"zen" moment when it all clicks into place for a noobie.  It's neat,
in a completely geeky way.

On Wed, Jun 9, 2010 at 6:49 PM, Larry C. Lyons <[email protected]> wrote:
>
> btw great summary Ray. Ever thought of doing a preso on this?
>
> On Wed, Jun 9, 2010 at 6:20 PM, Ray Champagne <[email protected]> wrote:
>>
>> For moving to production sites, I usually use an automated process in ANT or
>> using capistrano.  Essentially though, all those systems do roughly the same
>> thing tho - they do an export of the code to a releases folder in your
>> repository, then they move those files via FTP/Copy/RSYNC to the production
>> server. Exporting a site removes all the svn files/folders (which could be
>> thousands depending on the size of your app), making it a nice clean move.
>>  Adding it to a releases folder within the site's repository makes it very
>> very easy to roll back to a previous revision should all hell break loose in
>> production.
>>
>> Your repo should/could look like this:
>>
>> [sitename]
>> -- branches (this is used for changes to the site that may be drastic that
>> you'd want to keep on a separate track from your trunk)
>> -- tags
>>   --- releases
>>       ---- 06_09_2010.1 (this is an example of how we tag our releases)
>>       ---- 06_03_2010.1
>>       ---- 06_03_2010.2 (say that there were two releases that day, you'd
>> label it sequentially)
>> -- trunk (this is where you would have your main working code; where you
>> would normally check out from)
>>
>>
>> Kind of a "best practices" for SVN repo setups.  Hoep that helps and doesn't
>> cause even more confusion for you...
>>
>> [Cue Zaphod for the Git plug....]  =)
>>
>> Ray
>>
>> On Wed, Jun 9, 2010 at 4:59 PM, Cameron Childress <[email protected]>wrote:
>>
>>>
>>> If you are using tortoise you can just right click the working copy in
>>> windows explorer and choose "commit" to  check the code back into the
>>> repo.  You still move the files to your server however you already do.
>>>  I'd go into your FTP client though and create a filter for the little
>>> hidden ".svn" folders that are sprinkled all over your working copy.
>>>
>>> The best book I have seen on SVN is this one, which is free and online:
>>>
>>> http://svnbook.red-bean.com/
>>>
>>> -Cameron
>>>
>>> On Wed, Jun 9, 2010 at 3:58 PM, Medic <[email protected]> wrote:
>>> >
>>> > I've got an app I built a few years ago that until now I've versioned
>>> > manually. It's tedious as the app grows and I want to use a proper
>>> version
>>> > control tool. I downloaded Subversion and tortoiseSVN. I created a
>>> > repository (D:\Armis\Armis Repository\) on my work dev machine (XP w CF8
>>> > Developer Edition) and added all the most recent app files to it. So I've
>>> > "checked out" my repository to C:\Coldfusion\wwwroot\. So now what? I
>>> edit
>>> > the files then how do I check them back in? How to I upload the changes
>>> via
>>> > ftp? I'm a little confused. I use Homesite+ 5 for my dev so I assume
>>> there's
>>> > no direct integration. (It's still the best in my opinion.)
>>>
>>>
>>
>>
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion
Archive: 
http://www.houseoffusion.com/groups/cf-community/message.cfm/messageid:320950
Subscription: http://www.houseoffusion.com/groups/cf-community/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-community/unsubscribe.cfm

Reply via email to