All I ask is that Github implement Slack's Fair Billing Policy. Managing who at the organization can access a service is a silly task. Unfortunately, it doesn't appear that this follows that model. They're open to feedback: https://github.com/contact
I wasn't aware Slack had that model. It's really interesting.
The newfangled approach is something like HashiCorp's Vault, which is a dream when you're looking at more than half a dozen systems with similar roles. A different approach that I like to use for single or smaller cluster systems is Ansible's Vault and rolling out config files based on templates per environment. All actual config files are gitignored so I don't have do deal with conflicts on the server if I use a git…
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 the setup to essentially make it unchanged.
Bitbucket is ok for private repos. I think private repos are relatively secure there because Atlassian has much of reputation to loose if there is a security breach. Another plus for Bitbucket is the integration with Jira and other Atlassians tools. Beside that plus points I will rather go to GitLab.com (more features, better UI and integration with 3rd party) but my trust in private repos is lower there than on Bitb…
How could we convince you that at GitLab we take security very seriously?
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…
If every organization went to free alternatives, not only would those free alternatives need a source of revenue to support the new business, I think you'd find they too will change their pricing structure to better fit the people that use their product. One thing I also have to mention is a majority of for profit organizations have no problem paying for services they use. HN is a special snowflake on the internet, i…
On Gitlab.com's homepage[0] there is a giant product listing showing you exactly what you are saying they need to have: A source of revenue (GitLab Enterprise Edition).
If you no longer want/need the social aspects of GitHub, you can just move to GitLab. Much more affordable and you can self host it yourself. We have an on premise GitLab installation. Besides the rare upgrade, it's pretty hands off. And it's costing us $0 in licensing fees for over 60 users ;-)
We self-host GitLab as well for ~20 users and are very happy with it. We install every incremental update, which GitLab publishes very frequently -- weekly or several times a month. They are always seamless. The GitLab team is working so hard. https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELO...
god beware if your open source project needs a single private repository to share passwords between admins for example or private config for your webserver. Suddenly you see yourself at 394$ compared to the 7$ you paid before.
> beware if your open source project needs a single private repository to share passwords Passwords emphatically do not belong in git. Your private repos should be maintained such that accessing them would not compromise your security.
if you share Ansible inventory files that are encrypted with ansible-vault, then this is not happening. But i still wouldn't want to have a public repository with the files and the metadata of servers that is clearly not meant for public consumption.
Let me brig another example for OSS projects that could need a private repository: branches for security fixes that are not public yet.
If you no longer want/need the social aspects of GitHub, you can just move to GitLab. Much more affordable and you can self host it yourself. We have an on premise GitLab installation. Besides the rare upgrade, it's pretty hands off. And it's costing us $0 in licensing fees for over 60 users ;-)
I started using gitlab.com for that reason, but I will not stay there because it is too slow, to the point it is very annoying.
If you no longer want/need the social aspects of GitHub, you can just move to GitLab. Much more affordable and you can self host it yourself. We have an on premise GitLab installation. Besides the rare upgrade, it's pretty hands off. And it's costing us $0 in licensing fees for over 60 users ;-)
I looked at GitLab, it seems to come off second best in terms of features [1]. [1] https://www.visualstudio.com/get-started/overview-of-get-sta... Hard to argue with free though, if that's what you're looking for.
It seems most users here don't have gitlab.com in their radar and only mentioning Bitbucket as competitor. I've recently switched all my private personal repos to gitlab.com which also allows unlimited private repositories because gitlab.com seems to have better UI and more features than Bitbucket (when not buying any additional Atlassian Jira etc. products).
I see absolutely no reason why one would pay GitHub for private repositories when there is Bitbucket, or much better alternative to GitHub altogether - GitLab.
Yeah, this makes internally hosted GitLab VERY attractive for us now. Even the Enterprise edition is going to be significantly cheaper than GitHub.