configuration reorganization

[frnsys]

@ferristseng can you take a look at this and let me know if it looks ok?
cb36717

[frnsys]

@ferristseng are the configuration options supposed to be attached to the top level argos.conf i.e. argos.conf.AWS_ACCESS_KEY_ID or is it supposed to be nested by module name i.e. argos.conf.APP.AWS_ACCESS_KEY_ID? if it's the latter, then some of the default values in argos.conf.base don't get overwritten by the env-specific configuration files.

[ferristseng]

Everything should be nested by module name.

The config is loaded by module, so the call on load_conf_module(ENV), will load base settings into argos.conf module, but not argos.conf.development.app, which is where argos.conf.base is being redefined. A quick fix would be putting an import statement of argos.conf.base into argos.conf.developement.app.

I plan on rewriting the conf module, so that the base environment specific settings is loaded into a single module, say argos.conf.base.env. Then, there would be more 'templates' for more specific settings, that could contain unique settings, but also derive settings from values that are in the env.

Example:

import env from argos.conf.base.env

...
 CELERY_RESULT_BACKEND = "redis://%s:%s/0" % (env.database.redis.host, env.database.redis.port)
...

[frnsys]

Ok cool, I'll assign this to you then, thanks!

[frnsys]

I ended up making the config environment-agnostic, I don't think the app needs to know its env. the deployment system will just give it the config files appropriate for that env. see #79