421–430 of 662 posts
I find it quite hard to comprehend why people use Github for private repositories. There are many free alternatives. BitBucket seems to be the famous one, but Gitlab has grown into an amazing product with 3 different offerings; On premise community edition, on premise enterprise and hosted (like Github). We have used the on premise community edition for about 3 years now. I first installed it when you had to run abou…
Hmm, I still will use Gitlab instead of Github. Unlimited public and private repos for free is nice.
Does anyone know how Gitlab plan to sustain that?
Earlier quoted context omitted.
Does anyone know how Gitlab plan to sustain that?
a) They are vc funded b) They give things free to drive up adoption. For example, I don't think it will be free anymore if it was as popular as GitHub. Since that would not be sustainable. IMO, it's a poor decision by gitlab to give things out for free. Instead of innovating on features, they try to keep it cheap.
Earlier quoted context omitted.
Vendor lockin. Because there is a lot more involved that accessing files in a .git directory. All those CI systems and workflow plugins and whatnots such as travis-ci work with github, not git. And all the inflight issues and pull requests etc. Migrating or giving up the features you use has a cost (not just in dollars), and if github has done their sums right most customers will realize they are better off staying w…
Travis CI is pretty minor player (google search 10M > hits), and I would say 3rd party service integration is exactly vendor lockin. Imho this makes sense, because users who cared about pricing already moved on to cheaper alternatives and/or not used github to begin with. I agree, mass migration or phasing out github is unlikely because of the associated costs, however with all the other great services around new use…
For small private projects, gitlab.com has had unlimited private repos for $0/month for a while now.
I am strongly considering moving to gitlab.
I have some private repos on gitlab and it is sloooooooow to push and pull. It routinely takes 10 seconds to push or pull. That itself makes deploys seem like a chore. And it's enough to make me come back to github for a mere $7.
Earlier quoted context omitted.
I'm aware of the implications concerning the history, but sorry, the machine park is two machines. Setting up vault would just be total overkill. The people that have access to that repo change like once every few years. The repo will never go public. Let's keep the solution at least somewhat tailored to the problem.
Hey, I'm not arguing one way or the other. I like using Ansible for configuration in the way I work. I can trust that I can show my best friend and my worst enemy my project and they won't have the capability of making my life hell. Rock on though. Use the simplest solution for the problem at hand. If you're just managing two boxes though, I'd have a hard time coming up with an argument for adding more complexity to…
Everyone who is crying right now would be crying more if Github were to make the price free for private repos because with that, the amount of open source libraries they use would be cut in half.
Earlier quoted context omitted.
This was exactly the reason we used Bitbucket in the beginning, even if it was worse in some aspects. Github would have been simply too expensive (or restricting) with our "it's always in source control" approach, even for smaller prototypes. We're happy Gitlab users now by the way - and I'm curious how long Github will survive with their over-valuation as the alternatives get seriously better now - the lock-in and n…
Just wanted to add that if you don't want to run GitLab yourself our GitLab.com is free with unlimited private repositories but it also has also unlimited private collaborators https://about.gitlab.com/gitlab-com/
What's with all the negativity? This is really good pricing - all individuals now pay much less (a flat rate of $7), all small shops pay almost the same thing ($30 to $90 for 3 to 10 people). Both groups no longer need to think twice about creating repos, which has always been a huge pain that I've seen. I've even thought twice about microservices because the repo cost would be a pain. This will affect enterprises -…
> This will affect enterprises - but then they're either already on Github Enterprise or are used to per user pricing anyway my organization currently contains 15 github users. 2 of which are used by error reporting tools to open bugs (Sentry, Crashlytics), one of which is used by Jenkins, 3 of which are outside contractor for which github now will get the money multiple times as companies move to the same billing me…