Github Private Repos
I really wish Github had some free way to have private repositories. I'd even settle for a way to have unlimited private repositories for a reasonable paid price. I have a paid Github account for my company which has repositories related to that in it. But, that doesn't work well for random stuff that you would like to be private since you are limited to a specific amount of repositories.
I signed up for a Bitbucket account today just so I could host a private repository. I'll probably host ALL my random private repos there from now on. Thats a big missed opportunity for Github, because I'm sure there are a lot of people like me that are doing the same thing.
Github should remove the repository cap on their paid plans and instead have a simple storage cap like Bitbucket does. You should be able to have as many repos as you want that can fit in your space allotment.
Comments Post a Comment
The difference is they're trying to encourage open source. For stuff I don't want (or need) to be public, I keep on my local gito-lite server.
Sure, I typically just put short lived repos that I'm only accessing in shared Dropbox folders. But that isn't very good if you are collaborating with non-git savvy people (using issue trackers, etc).
I have some very long-lived repos hanging around. For instance, my configuration management is stored in git. It holds the configuration of each of my machines, along with sensitive information like passwords. Not an issue of copyright, merely one of security. So that would be useful to have a private repo for. But then again, the fact that I have something like that that I need to store in a repo probably means I have a place to store it in the first place.
Still, I agree with their stance from the standpoint that it does encourage people to make their projects open source.
The difference is they're trying to encourage open source. For stuff I don't want (or need) to be public, I keep on my local gito-lite server.
Sure, I typically just put short lived repos that I'm only accessing in shared Dropbox folders. But that isn't very good if you are collaborating with non-git savvy people (using issue trackers, etc).
I have some very long-lived repos hanging around. For instance, my configuration management is stored in git. It holds the configuration of each of my machines, along with sensitive information like passwords. Not an issue of copyright, merely one of security. So that would be useful to have a private repo for. But then again, the fact that I have something like that that I need to store in a repo probably means I have a place to store it in the first place.
Still, I agree with their stance from the standpoint that it does encourage people to make their projects open source.