3 ms·
I couldn't agree more. It has annoyed me when companies charge more for decisions about how you choose to do something - in this case how you split up your code
by asher_ 10y ago
I couldn't agree more. It has annoyed me when companies charge more for decisions about how you choose to do something - in this case how you split up your code. Paying per person makes much more sense.
- endymi0n 10y agoThis 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 network effects are quite shallow IMHO.
- sytse 10y agoJust 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/ https://about.gitlab.com/gitlab-com/
- ciokan 10y agoAny API on this service?
- sytse 10y agoSure, see http://doc.gitlab.com/ce/api/ http://doc.gitlab.com/ce/api/
- ciokan 10y agoThe interface is horribly (painfully) slow. On the API side...any of the params I post when hitting the create project endpoint are not taken into consideration. With the following data posted to the API I still get public builds, issues not enabled, wiki not enabled and so on: {'issues_enabled': True, 'description': None, 'visibility_level': 0, 'public_builds': False, 'wiki_enabled': True, 'snippets_enabled': True, 'merge_requests_enabled': True, 'name': 'testfoo'}
- johntash 10y agoI never realized gitlab.com offered free private repos. Thanks!