61–70 of 198 posts
It's free for up to 2 users. Unlimited repos and disk space.
Cheers, to you for adding some competition to the marketplace. I hope it provides some pricing pressure on Github one of these days.
The title of the page at www.codeplane.com is "Unlimited private Git hosting", yet it appears that you are limited to 2GB of repositories for your $9/month. How is this unlimited? Are there other plans that you can sign up for? If so they seem impossible to find on the site.
I just use bitbucket.org + Mercurial. More than enough for personal projects, or more, given that it's unlimited. The only limit is amount of users. Switching to Hg was a bit of work, but I've actually learned to like it more than Git. Really though, it's the same kind of thing and I just use both. So I ended up at bitbucket for the same reasons OP built a new site. My way was quicker though.
I think CodePlane is very cool, but it seems to solve a different problem than the one advertised on the blog. To save my repos "for posterity" on Github without incurring a $100/month bill, I simply create a master repo (say old-projects/) with all my unused repos in it. On the other hand CodePlane seems to be a great solution for collaborative work on lots of private repos. This can save big bucks. I love to see pr…
Its like a ford salesman asking you about how you plan on using your ford focus, oh you will be driving to work? Highway driving costs you 50% extra. Sorry. You can take our back-alley car for cheap though.
as arturadib mentioned, you can make the "old-projects" repo. But that's just a hack/workaround for a wrong business model. Though I am sure this business model is much more profitable.
You can set something like this up on any VPS with gitolite ( https://github.com/sitaramc/gitolite ) pretty easily. gitolite lets you set up very fine-grained per-user/repo/branch permissions, manage your users' SSH keys, and gives you nice clean git@git.you.com:repo-name access to your remotes. I've done this for myself with a $48/year VPS from prgmr.com specifically because I needed more private repos than Github c…
...or gitosis http://scie.nti.st/2007/11/14/hosting-git-repositories-the-e... Gitosis does not have as fine grained control as gitolite nor is it as well documented (config file errors are hard to debug), but it works well within its limitations. Both are now available as Debian/Ubuntu packages (gitolite was not when I started using gitosis). The other obvious difference is that gitolite is written in Perl and gitosi…
Maybe I'm not fully understanding this.. If I don't need the web interface and public code sharing, why would I use this verse getting a Linode instance and installing git there.
> If I don't need the web interface and public code sharing, why would I use this verse getting a Linode instance and installing git there. Private code sharing. You have to install something like gitolite (see my other comment) to do private code sharing with git on a VPS, or you'd have to create a system-level user for every person you want to share code with.
It is one of their "one-click" installations and I have been pretty happy with it for my limited use.
You can set something like this up on any VPS with gitolite ( https://github.com/sitaramc/gitolite ) pretty easily. gitolite lets you set up very fine-grained per-user/repo/branch permissions, manage your users' SSH keys, and gives you nice clean git@git.you.com:repo-name access to your remotes. I've done this for myself with a $48/year VPS from prgmr.com specifically because I needed more private repos than Github c…
...or gitosis http://scie.nti.st/2007/11/14/hosting-git-repositories-the-e... Gitosis does not have as fine grained control as gitolite nor is it as well documented (config file errors are hard to debug), but it works well within its limitations. Both are now available as Debian/Ubuntu packages (gitolite was not when I started using gitosis). The other obvious difference is that gitolite is written in Perl and gitosi…
Gitolite on the otherhand is under active development, the documentation is great, and the author is generally available on the #git channel as are many other active users of the software.
While I do agree that Github leaves space for a model like this, I think the value of Github is that it offers a great community and awesome toolset (online and offline). Then I read this: "I also wanted to do almost everything from my terminal, so I built a CLI, that you can use to manage repositories, public keys and collaborators. For daily usage, you probably won't have to go to our web interface ever again, and…
Yeah! One can always set up the whole thing, but for small shops and freelancers it makes no sense to manage something like this. Maybe for hackers like us... ;)