Re: Git, CF and best practices
Thank you all for the information. I will be reading a lot and trying to make the best decision! On Tue, Aug 31, 2010 at 12:24 AM, Kym Kovan dev-li...@mbcomms.net.auwrote: On 31/08/2010 11:16, Mallory Woods wrote: I just started looking a git to use for source control for our CF projects. I wanted to ask those who are using it a few questions. git is a distributed version control system so having a central repository is fine for later, completed versions but it might be worth considering having a local repo for each developer so that they can save and version control internally and then when they are happy with their current work snippet push that back to a common/shared repo. That way you get some independence otherwise you are not doing much more than what svn does. Also you might consider looking at mercurial rather than git as it has a better fit with Windows machines. For example here we use Mercurial and every developer has a local set of repos on their workstation which they work with and when they have finished code synchronise from that back to a central repo where they can share their work with others. We actually have several central repos for test/stage levels of goodness of code rather than branching, the two are almost synonymous in distributed version control systems and synchronising between repos is simplicity itself (in Mercurial at least). If you want to get really fancy and you have developers on the move or with more than one workstation, desktop and notebook for example, then you can have another repo on a central server for that developer to sync up to from one workstation so that they can then pull that update down onto their other workstation. They can then keep code current on two machines without having half-good code in the main repos for other people to trip over. -- Yours, Kym Kovan mbcomms.net.au ~| 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-talk/message.cfm/messageid:336664 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Git, CF and best practices
I'm not a git user myself, but here is a recent blog article I remember seeing: http://www.bytestopshere.com/post.cfm/git-is-scary-but-it-doesn-t-need-to-be -Matt On Mon, Aug 30, 2010 at 9:16 PM, Mallory Woods mallory.wo...@gmail.com wrote: Hello all, I just started looking a git to use for source control for our CF projects. I wanted to ask those who are using it a few questions. First a few facts: Our servers are running Linux (dev, staging, production) but we are writing our code on Windows boxes. We are using CF builder and I have the git plugin installed. I wanted to ask about setting up the git repository on the server to be in our web server directory? For example: the web directory is http://www.thissite.com and the local directory is : /var/www/html/projectname Would it be best to put the repo there in the project directory and create two branches for the two developers and merge them when we want to release the code? I would also like to ask, if anyone has any good suggestions on a tool or tools to push a specific version of the code to the server(s). From what I can see I would do an export then manually unarchive the files to the proper directory Thanks in advance. Mallory ~| 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-talk/message.cfm/messageid:336658 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Git, CF and best practices
You may find this presentation may help. http://experts.na3.acrobat.com/p65645730/?launcher=falsefcsContent=truepbMode=normal Also Mike Henke (http://www.henke.ws/) blogs about using .git with CF on a regular basis. hth, larry Hello all, I just started looking a git to use for source control for our CF projects. I wanted to ask those who are using it a few questions. First a few facts: Our servers are running Linux (dev, staging, production) but we are writing our code on Windows boxes. We are using CF builder and I have the git plugin installed. I wanted to ask about setting up the git repository on the server to be in our web server directory? For example: the web directory is http://www.thissite.com and the local directory is : /var/www/html/projectname Would it be best to put the repo there in the project directory and create two branches for the two developers and merge them when we want to release the code? I would also like to ask, if anyone has any good suggestions on a tool or tools to push a specific version of the code to the server(s). From what I can see I would do an export then manually unarchive the files to the proper directory Thanks in advance. Mallory ~| 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-talk/message.cfm/messageid:336659 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: Git, CF and best practices
On 31/08/2010 11:16, Mallory Woods wrote: I just started looking a git to use for source control for our CF projects. I wanted to ask those who are using it a few questions. git is a distributed version control system so having a central repository is fine for later, completed versions but it might be worth considering having a local repo for each developer so that they can save and version control internally and then when they are happy with their current work snippet push that back to a common/shared repo. That way you get some independence otherwise you are not doing much more than what svn does. Also you might consider looking at mercurial rather than git as it has a better fit with Windows machines. For example here we use Mercurial and every developer has a local set of repos on their workstation which they work with and when they have finished code synchronise from that back to a central repo where they can share their work with others. We actually have several central repos for test/stage levels of goodness of code rather than branching, the two are almost synonymous in distributed version control systems and synchronising between repos is simplicity itself (in Mercurial at least). If you want to get really fancy and you have developers on the move or with more than one workstation, desktop and notebook for example, then you can have another repo on a central server for that developer to sync up to from one workstation so that they can then pull that update down onto their other workstation. They can then keep code current on two machines without having half-good code in the main repos for other people to trip over. -- Yours, Kym Kovan mbcomms.net.au ~| 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-talk/message.cfm/messageid:336660 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
