| { |
| "name": "CRUConfig", |
| "version": "1.1.1", |
| "summary": "CRUConfig is an objc implementation of dotenv. It is a wrapper to config.plist, giving you an easy way to get API keys out of your code.", |
| "description": "CRUConfig is an objc implementation of dotenv. It provides a wrapper to config.plist, giving you an easy way to get API keys and urls out of your code, while having your IDE autocomplete your values now that they will be properites instead of stings. It is also environment based so you can define different config files for different environments.\n\nThe pod will look for a config file that matches the name of your current configuration.\ne.g. If you are building your debug configuration it will look for config.debug.plist in your application bundle. If you build a target with your release configuration it will look for config.release.plist. If you create a custom configuration for your project called beta and your build uses that configuration then the pod will look for config.beta.plist. Note that they are alway in lowercase.\n\nIf you don't want to do configuration specific config files you can just use config.default.plist or config.plist.\n\nThe order of priority is as follows:\n * config.<current build configuration name>.plist\n * config.default.plist\n * config.plist", |
| "homepage": "https://github.com/CruGlobal/CRUConfig-ios", |
| "license": "MIT", |
| "authors": { |
| "Harro": "michael.harrison@cru.org" |
| }, |
| "source": { |
| "git": "https://github.com/CruGlobal/CRUConfig-ios.git", |
| "tag": "1.1.1" |
| }, |
| "platforms": { |
| "ios": "7.0" |
| }, |
| "source_files": "CRUConfig/Classes/**/*", |
| "pod_target_xcconfig": { |
| "GCC_PREPROCESSOR_DEFINITIONS": "CRUCONFIG_CURRENT_BUILD_CONFIGURATION=$(CONFIGURATION)" |
| } |
| } |
