Do I need GitHub?
-
Florian Rappl wrote:
If you need something for internal projects, then GitHub is a weird choice anyway, as you could just go with, e.g., a GitLab instance, which is installed on premises
Agreed. My point was that GitHub is not an appropriate place for proprietary code, the advantage of being able to access your code from anywhere being offset by the lack of security.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill
Yep, that's definitely true!
-
It seems like everybody is on GitHub nowadays. I'm not looking for source control or collaboration tools. I could share my code, but why would I? I don't have anything very interesting to share at the moment (or maybe some files for my blog/articles?). And I'm also not looking into contributing to other projects as I'm busy enough studying for my Open University courses. I understood GitHub is more than that (a social network? Can't be better than CP :)). I am kind of interested in what all the fuzz is about, but is it worth it for me to create a profile?
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}Sander Rossel wrote:
I am kind of interested in what all the fuzz is about
If one develops code, anywhere, then one should consider how relevant source control and back up are. The two are not the same. If one decides that either is prudent then one must then decide on a solution for that. Github fulfills the need for one, and might fulfill the need for the second since one might presume that github backs up its own content. (One should however verify the second.) In general from a professional point of view I wouldn't suggest relying only on a single business for a technical solution because businesses can and do run into trouble. But often it is sufficient to have ones content locally and then on an external source. However for a business (more that a couple of people) that probably isn't sufficient since there is data which is unlikely to be preserved on individual developer machines. That might be different when talking about a single individual however.
-
I don't know if that last statement is a valid point against GitHub. If you use it for OSS projects, then you don't mind anyway [anyone can clone anyway - the license itself is very clear stated]. If you need something for internal projects, then GitHub is a weird choice anyway, as you could just go with, e.g., a GitLab instance, which is installed on premises. This gives you much more freedom, however, comes also with additional maintenance costs.
Git doesn't actually need a server. The only reason I can think of to use one is if you absolutely love web interfaces. Personally, I haven't found anything yet that I like better than GitExtensions, so even when I do use GitHub it's just cloud storage. For internal projects, just clone a "public" repo to a folder on an internal server. You can easily restrict access via your existing authentication system (ActiveDirectory in our case) if that's your bag, so no need to muck about with keys for ssl or anything. Easy-peasy, and very low maintenance.
-
Git doesn't actually need a server. The only reason I can think of to use one is if you absolutely love web interfaces. Personally, I haven't found anything yet that I like better than GitExtensions, so even when I do use GitHub it's just cloud storage. For internal projects, just clone a "public" repo to a folder on an internal server. You can easily restrict access via your existing authentication system (ActiveDirectory in our case) if that's your bag, so no need to muck about with keys for ssl or anything. Easy-peasy, and very low maintenance.
I don't know where you read that git needs a server (no one said or implied that). The discussion was about a central web interface with the special case of GitHub. However, running git without a server is only a half-baked solution. If you have source control you also (should) want backups. Therefore syncing with one or more peers is important. And I also don't see where your reasoning against web interfaces is coming from. Even at home I use gitweb on my RPi - its often the fastest and most convenient way to access quick information about a repository that has not been cloned or fetched yet.
