What are main differences between Git, GitHub and Bitbucket resp Gitkraken? And also Git and Mercurial
Git and mercurial(hg) - both are the actual tools for version controll. In fact both them can be called “Distributed Version control system-tolls”, While git and mercrurial can be called true vanilla version controlling ‘tools’ which can be used for the creation, management and version controlling of git/hg repositories,
well - i have heard that we can use git with (on) Github and bitbucket. Is this true: Can i run git on both systems GitHub and bitbucket. That would be great.
first of all: - afaik i can use Bitbucket with GIT - is this true?
So, these are some of the major differences. There are prolly several other minor differences that one might realize once you use both of them.
The question is: Which Git GUI should I use with GitHub, Bitbucket or GitLab? A friend of me told me that i should run (use) GitKraken
Gitkraken is told to be a commercial project that only wants to make mone.y
but technically spoken gitkraken has some interesting features.
GitKraken connects to all 3 to clone/add repos, create/view PRs & more. Free for Windows, Mac & Linux!
So the question is: should loook at gitkranken or stay with GIT, Github and Bitucekt
and leave gitkraken as a tiny commeercial project that is not worth looking at
On Mon, 17 Dec 2018 20:36:03 +0000, Knurpht wrote:
> My advice: learn how to use git on cli. It’s not a steep learning curve,
> basic commands are trivial from a cloned git compatible repo. And, it
> will work with any URL from an accessible git server.
Agreed. Git is pretty easy to learn from the CLI.
As for the other questions, I would suggest asking in a git community for
more detailed answers.
So, what really is the difference between the various cloud repositories?
Actually, if you are only interested in a convenient, cloud-based repository with version control, all that you listed do that. And, you didn’t even mention probably the two oldest (one defunct) grand-daddies, Sourceforge and Freshmeat (Those were the days when they were really the only two choices).
The exception to the list you’re asking about is gitraken.
I think I ran into this awhile back, it’s not a cloud repository service, it’s a client which is why you say you can use it to connect to many different git repository services (and none of its own because it wouldn’t exist). Go ahead and try it if you wish, but there’s a reason why it costs… It’s offering features and perhaps ease of use that its competition including the free clients most people use don’t have.
Use Gitraken if you wish (and there is a free Git GUI as well), but I strongly advise you to learn as much command line as possible. The basics aren’t difficult to learn, and if you can at least do those basics, then you’ll be able to work on any machine anywhere (you just need to have git installed) and won’t have to install some special app which may also have restrictive licenses on how times you can install on different machines. This might be particularly important if for instance you use virtualization like I do to isolate projects and setups from each other.
Although git is all the rage now (and for good reason), it’s not the only version control system that can be used. One alternative is Mercurial, which you mentioned but there are also a few more (I imagine Wikipedia can be more complete). For years Microsoft Developers used its own Team Server and Service (but due to demand has been migrating to git, and especially now that MS has bought Github). There are also version control systems that specialize in different use, different capacity, different features. If you’re curious about that kind of stuff you can do an Internet search on topics like “Why I hate git”
You may also wonder why everyone talks about Github, and why it seems to be the primary choice for practically everyone. The primary reason is that it pioneered the idea of melding the version control repository with social media, enhancing and promoting co-operation and collaborating and just finding code, both snippets and entire applications. When you create a repository, it’s encouraged to be made public for anyone to find and view (It’s free). If you want to create a private (non-public) repository, you have to pay for it (some competitors offer modifications of this allowing free, limited private repos).
Besides the repository/social media innovation, Github can also be home to your billboard type website at absolutely no cost (Yes, completely free) with very high level Provider reliability (5 nines?). In fact, the entire infrastructure and service Github offers are offered with a similar commitment to the same reliability everywhere. You might find the following article interesting, the biggest attack the world has seen to date hit Github this past summer but most people (general public and Github Users) hardly noticed…
All free, no cost. Many people run their blogs and commercial websites this way.
Point your Domain to the website using DNS and no one would know that your website is deployed for free on Github and now your only cost is the Internet Domain and maybe DNS (unless you use a free service, yes those exist, too).
Or, if it doesn’t matter to you, just use the Github URL (like above)
No server-side functionality.
No databases unless you want to deploy it as a publicly accessible file (and there’s not much security to that).