adding django-configuration to requirements and changed manage.py to use it
adding django-configuration to manage.py and wsgi, to load info from the envs
no more need for this, since handled in the manage.py/wsgi.py
settings base using django configurations
configurations for local
configurations for production, adding django-heroku-memcacheify to get the memcacheify as an env var
from heroku
fixing things up, that were breaking in the import
forgot the static_url in production... oh my....
since the server is not running with the wsgi.py in prod, then explicitly tell
what is the config that should use (or could set this as a env_Var too: DJANGO_CONFIGURATION=Production that would work also)
avoiding problems with the secret key, and django 1.5 that seems to be very strange
checking if by setting the settings it will work the procfile
since it won't work with this option been set, then it'll have to be by env var