3 ms·
I used gitolite on a VPS previously and it worked well, but when Bitbucket introduced free unlimited private repositories I switched. IMO there is no reason to
by masnick 13y ago
I used gitolite on a VPS previously and it worked well, but when Bitbucket introduced free unlimited private repositories I switched.
IMO there is no reason to use gitolite now for unless you have (a) sensitive repos (with your own server, not a VPS of course), or (b) lots of private repos with lots of collaborators and you have no money for a Github or Bitbucket monthly fee and you aren't a non-profit (I think non-profits can get a free Bitbucket account).
That said, I'm interested to hear about other gitolite use cases I haven't thought of.
- LordIllidan 13y agoYou can still use bitbucket on your own hardware with http://www.atlassian.com/software/stash/pricing http://www.atlassian.com/software/stash/pricing (Not affiliated with Atlassian/Bitbucket in any way - but I love their software)
- thepumpkin1979 13y agoTotally. We use github for everything, but in this case, we are hosting a private repository since we need to trigger a compilation of code in a builder/worker of the cloud app we are developing. We modified the beginning of the post to clarify what our goal is by hosting privates repos with gitolite.
- Pyrodogg 13y agoCouldn't you have done something similar with Github's web hooks? Something like have it ping the build server when a commit is made on master which pulls the code and builds? I'm just curious why the need to trigger builds jumped pushed you all the way to hosting it on your own.
- robmil 13y agoThere's also the issue of repository size; both BitBucket and GitHub have (entirely reasonable) fair use policies that seem to limit repos' sizes to 1GB or so. Yes, Git sucks with big files, but sometimes it's necessary to exceed this total size.
- sharagoz 13y agoIm in the process of moving from self hosted (VPS) git server to Bitbucket as well. Github was just too expensive for me but when I discovered that Bitbucket was charging pr user instead of pr repo, switching was a no brainer.