iorewgogo.blogg.se - Coda 2 git tutorial

CODA 2 GIT TUTORIAL HOW TO
CODA 2 GIT TUTORIAL INSTALL
CODA 2 GIT TUTORIAL PRO
CODA 2 GIT TUTORIAL CODE

Branches and tags are references to commits, commits that are referred to along with their ancestors are the ones that are kept. A commit is what actually contains metadata if you will of history. a branch is not actually some kind of record of your project, a branch is just a 40 byte file. This will help you understand the nuances of merging, rebasing, having a balanced history.

CODA 2 GIT TUTORIAL PRO

and Scott Chacon's Git Internals (similar to the book but not the same is Chapter 9 of the Pro Git Book, same title, same author, still find Git Internals better).

For that I highly recommend the following: Once you have a feel for it it will help immensely to have a better understanding of the inner workings of Git. ( SourceTree was recently released for Windows, I've been using it on the Mac myself it's been great.) Also have a git GUI client handy if just to see the history. Simulate an actual need in EE that isn't being fulfilled, use the resources others provided to get from A to B, try to use command line for the commands.

CODA 2 GIT TUTORIAL CODE

Have a history of all the changes you made whether in your templates or add-ons (this is especially great when code you introduced.Making a quick fix for production site while working on major changes for development without losing anything.

Flipping between snippet/template code for a development vs.

Managing assets/scripts/libraries/whatever shared between sites.

on GitHub you can copy someone's git repository verbatim as if it was one of your own and modify it to your heart's content!) I highly recommend first playing around a little with git to get it to help you achieve a few objectives. After much research and playing around I wound up using git submodules as the problem wasn't with this aspect of git itself, but with my misunderstanding of the inner workings of git. If you're new to git you're likely to mess something up there down the line. I was trying to avoid git submodules like the plague because of my past experience with them (Drupal).

CODA 2 GIT TUTORIAL HOW TO

Having just gotten at least my development site up and running with Git I was looking into how to manage all the different parts of an EE project as sub projects (repositories). And if there are any database considerations with this.

CODA 2 GIT TUTORIAL INSTALL

I'd be interested to hear the communities best practices in regard to managing one base boilerplate install to keep core files and third_party files up to date across all sites - if indeed that is possible. Instead of GitHub or BitBucket I have used Beanstalk - primarily because it has a neat 'Deploy to FTP' function which speeds up deployment. With that said, GitHub's Windows app is quite good. I have noticed that the applications on Mac are considerably easier to use than their Windows equivalents.

I would clone this for each site I built and have the third_party resources and basic channels I constantly use ready to roll in minutes. In the past I have run an install of ExpressionEngine that has been the basis of a boilerplate. The core files, third party plugins and your design of course should be - but version controlling the /images/ and /cache/ directory for example is over the top and is a burden on resources (and frankly a waste of time!). One of the key things to remember with ExpressionEngine and GIT is that not all directories should be version controlled.