site configuration

[amitu]

I have implemented the configuration system I proposed. By relying on django configuration we do not have to learn anything about how to access configuration when writing plugins.

[amitu]

Oops, I should have started using git flow stuff from beginning. I guess I ll have to wait till first pull request is accepted. Next pulls requests would be cleaner I promise :-)

[amitu]

My justification for not using config.json already there: it contains sensitive data, I expect to checkin config file along with rest in public places. As mentioned in another issue I feel entire s3 support should go in favor of s3cmd based solution, which means we should get rid of config.json, config.py and site.upload() method.

[hypertexthero]

+1 for ability to set extra site configuration variables. For example, I want to be able to use Markdown Extensions and Typogrify. Currently getting by with requiring typogrify in setup.py and adding it to installed apps in site.py to be able to write posts like these.

[koenbok]

I've left this here way too long without commenting, but I'm hesitant to add this because it adds a lot of complexity in my mind (an extra second config file, a new library, a new syntax to understand).