News for hackers. Stuff that matters.
Re:Don't include configs in your Git repos by dvanduzer on Wednesday October 28, 2015 @11:18PM (#10469030)
When you're running a SaaS business, your configs are your code in many cases.

Version control is incredibly important for scaling operations. To keep things manageable at scale, you also need to separate concerns properly. But this just means you shouldn't do things like have your configuration API refer to its own repository to configure itself.

edit: CocoaPods in particular is a weird artifact that I suspect will go away now that iOS is supporting dynamically linked frameworks.

Re:Don't include configs in your Git repos by seivan on Wednesday October 28, 2015 @11:32PM (#10469096)
Some of us like CocoaPods offering source dependencies instead. Makes it easier to learn, debug and fork. That being said, the quality has gone downhill.

Besides it's easier to manage your dependency in a Podfile than submodules.

Re:Don't include configs in your Git repos by dvanduzer on Wednesday October 28, 2015 @11:45PM (#10469141)
Managing your dependencies on external bits is distinct from someone upstream dealing with the packaging and distribution of those external bits.
Re:Don't include configs in your Git repos by seivan on Thursday October 29, 2015 @07:40AM (#10470292)
Those bits won't change that much over time once the project becomes stable. It's not much of an issue.