[hmm, wrote this on the train this morning, lost internet and
subsequently replied to a different message on my phone, could be this
post overlaps by a lot, oh well]
On 9/24/14, 6:59 AM, Ted Roche wrote:
Git will work with whatever host you choose, as well as letting you keep
local repositories. You don't have to host your git anywhere other than
local, but it's good to keep it out of the office in case of disasters.
BitBucket.com lets you host public or private repositories at no cost.
GitHub charges for private repos, but is_the_ place to host and share and
locate public, open source repos.
GitHub is really awesome. I like to use it whenever possible, and have
been attempting to put all my open source stuff up there as I move away
from Subversion. I've contracted with a couple companies wanting to use
GitHub and we set up private GitHub organizations and repositories for
that, and it works very well, but GitHub still has the data and for one
of the companies I work for, that just isn't acceptable. So I set up an
internal, self-hosted instance of Gitorious, a GitHub-like platform for
hosting projects, repositories, and wikis. GitHub has this option too
(Enterprise) but it isn't free and in the face of having to get a PO
approved or not, which would have required lots of justification
meetings ("we already have Microsoft TFS, why pay for another?") I chose
free and moved on with my project.
I'm also hosting some of my client repositories on my own
infrastructure, using simple SSH access using my SSH credentials to that
box sitting in my datacenter. This comes out of the box with Git.
One of the best things about distributed source control (or maybe it's a
git-only feature, I don't actually know at the moment) is that when you
clone a repository to your local computer, you have the entire
repository including all branches, tags, and change history. So when you
do a diff or merge between any two commits, no network access is needed.
In fact, when you do a commit, no network access is needed. The only
times you need to access the network is to push your commits up, or to
pull other's commits down.
Git's much simpler than reading the man pages would lead you to believe.
After a couple months using it daily, you'll be a pro at what you need
to accomplish with it, and you'll see tangible productivity gains
compared with non-distributed source control solutions such as Subversion.
Paul
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
