Earlier quoted context omitted.
Git is just a format for storing data with a record of how that data changed. Saying you shouldn't store it in git seems rather like saying you shouldn't store it in btrfs. It's true that if your btrfs disk image becomes public, the data is recoverable, and it's hard to reliably scrub deleted files from btrfs, but that doesn't mean it's the wrong tool for a filesystem (or a repo) that stays entirely internal. Saying…
A git repo is usually shared over multiple machines/developers. So the chance of someone publicating it is larger. As well as the entire history is usually copied everywhere
Introducing unlimited private repositories
531–540 of 662 posts
Re: Introducing unlimited private repositories
#532Earlier quoted context omitted.
If you are non profit and open source do you really need private repos?
In a non-profit that I collaborate with [1] we use private repos to keep the server setup and some tickets that contain sensitive information (user data). All other code is open source. Obviously we don't want to keep api keys etc. in the public repos. [1] https://github.com/sozialhelden/wheelmap
Re: Introducing unlimited private repositories
#533Earlier quoted context omitted.
I've used Bitbucket in the past. They charge per-user[1], and their pricing is significantly better free for 5 users and then once you eclipse 5 users it's $1/user up to 100 users and then $200 for unlimited users. [1] - https://bitbucket.org/product/pricing
This. I use bitbucket too and I can't understand why people are still paying github when bitbucket does exactly the same and is free.
Re: Introducing unlimited private repositories
#534Earlier quoted context omitted.
What the hell? Are you defending a decision to keep keys unencrypted in a git repo?
yes, indeed I am. I'm all in favor of keeping the tools used to a level where the effort makes sense to protect the value of the goods. I totally could lock up my newrelic api key in a bank safe, double encrypted with two persons 4096 bit GPG keys, but that would be a little overkill, wouldn't it? Do you do that? I'd be moderately annoyed if somebody started pushing false metrics to my NR account, but that's about al…
Re: Introducing unlimited private repositories
#535Earlier quoted context omitted.
If $8 is a big deal per user, how little are you paying the poor bastards?
I guess he's not paying his employees 900% market rate, why would he pay 900% market rate for GitHub instead of BitBucket? Just trying to point that your logic doesn't check out. I personally like the new pricing, but as a non-paying user of GitHub and BitBucket... I'll stick to BitBucket for my private repos :) I guess they don't give a damn as I'm still not paying either :)
Re: Introducing unlimited private repositories
#536Earlier quoted context omitted.
"that we're not developing in the open" Honest question... why? I totally understand the mindset of "gotta go all secret squirrel to protect our profits" but if your org isn't in it for the profits there's not much to protect? I have seen examples of people performing very naughty acts like private repos to hold plain text passwords, plain text cloud service keys, plain text corporate credit card numbers for expense…
There are a ton of reasons not to develop in the open, no matter what your structure. - You're experimenting - You don't want comments from the peanut gallery while things are in progress - It is not for external use, specific to an institution or project, or otherwise nobody else will care - It deals with something sensitive - You've made an agreement with someone else that requires it - etc. etc. etc. People seem t…
Re: Introducing unlimited private repositories
#537Earlier quoted context omitted.
This. I use bitbucket too and I can't understand why people are still paying github when bitbucket does exactly the same and is free.
People use github over bitbucket if they like the features that github provides, the diffs, issues etc. Not sure which features are unique to github alone, but each provider (including gitlab) has their own flavor. Many are just used to github flavor.
Re: Introducing unlimited private repositories
#538Earlier quoted context omitted.
In a non-profit that I collaborate with [1] we use private repos to keep the server setup and some tickets that contain sensitive information (user data). All other code is open source. Obviously we don't want to keep api keys etc. in the public repos. [1] https://github.com/sozialhelden/wheelmap
And you share the passwords with enough volunteers that per users pricing becomes a problem?
Re: Introducing unlimited private repositories
#539Earlier quoted context omitted.
In a non-profit that I collaborate with [1] we use private repos to keep the server setup and some tickets that contain sensitive information (user data). All other code is open source. Obviously we don't want to keep api keys etc. in the public repos. [1] https://github.com/sozialhelden/wheelmap
And you share the passwords with enough volunteers that per users pricing becomes a problem?