mykabam/kabam — pull request #40 by chopachom (2013-10-02 12:51:49+00:00)
Title: feat(config): use toml and new naming scheme

This request changes config format from json to toml and changes naming convention from cameCase to ALL_CAPS
The main problem with json config is that it doesn't have comments and comments like this

```
"__comment": "Values prepended by __ are comments to actual values, without __ on the beginning",
"__service.json": "This config file contains sensitive information, that can be overriden by enviromen
```

are hacks and just look terrible I think, you open up you config and you have to parse with your head to distinguish between real values and these comments.

And since we decided not to use yaml, i think toml would be ideal format for this:

- it is crazy simple
- it maps 1:1 to json
- it has comments
- it resembles ini files

Another thing i removed is two configs - one for sensitive and another for insensitive information. The reason for that is that keeping configs in VCS is by definition a bad idea, it doesn't matter if it doesn't contain sensitive information - the purpose of the config is to be customised on the machine the code runs on. For example one developer has `loglevel` set to 5 and another to 2, whose version would be committed to the repo? I think we should expect that user's wouldn't put their configs in the VCS because it's inherently wrong idea and so we don't need two configs.