Docker to run the project using local environment vars

Hi there,
Github spoiled the surprise here.. but yey \o/ a docker to run the project =)

I'm also using [Fig](http://www.fig.sh/) to make link the containers used, and set the environment vars more easily.

Here how it works:

All dockers are located in `dockers` folder.

# DB
There is a DB container (PostgreSQL) that uses this env vars to build a empty table, ready to use:

    - USER=ccbv #DB user
    - DB=ccbv #DB name
    - PASS=ccbv #DB user pass

So when this container start it will prepare a postgresSQL server with that info. Also the all PG data can be accessed from the host machine inside: `./dockers/docker-postgresql/data`.

# Django App
The django app container uses this env vars:

    - USER=admin2
    - USER_EMAIL=admin2@example.com
    - USER_PASS=pass2
    - STATIC_URL=/static/
    - DEBUG=True

where `USER`, `USER_EMAIL` and `USER_PASS` are used to create an super-user automatically.

The django container is linked with the DB container, and whenever it starts it will do this:

* setup the `DATABASE_URL` env var to point to the address of the connected DB container, with the user, password and database name needed to connect, all got from available env vars.
* run `pip install -r requirements.txt` (if it's the first time then it will install everything, if not it will just check if there is something new).
* wait until the DB container is ready to accept connection, just in case the DB container take a long time to start.
* **if** is the first time the container is running:
  * ensure the DB is clean (will drop all tables using `manage.py reset_db)
  * sync the DB
  * run the DB migrations
  * load the fixtures (`project.json`, and `1.3.json`-`1.7.json`)
  * create the super user (with the environment variable passed to the container)
* **if its not** the first time it's running, then:
  * will run the DB migrations just to make sure that there are no new migrations to be run
* and to finish it runs django, with `manage.py runserver 0.0.0.0:8000`

# Checking the logs:
After you start the containers with `fig up -d` they'll run in background, so if you want to check in what step of the process they're in, just run:

    fig logs

# Stopping the containers:
To stop a container (will keep the volumes) just run:

    fig stop

# Starting stopped containers:
If the containers where stopped and you want to bring them back again in the same state as they where, just run:

    fig start

# Django reloading on change
Since the hole project folder is added to the container at the time that it runs (not when it builds) whenever you change something locally in the project, this will affect the container app, and so you'll still be able to take advantage of Django's server reloading on change to anyfile


And I think that's it.

This is another problem known, and as described in https://registry.hub.docker.com/_/postgres/: 

> If there is no database when postgres starts in a container, then postgres will create the default database for you. While this is the expected behavior of postgres, this means that it will not accept incoming connections during that time. This may cause issues when using automation tools, such as fig, that start several containers simultaneously.

So I found this little *"hack"* that keeps checking the linked container to see if it's responding ok, after the DB is ready, it will stop this loop and follow to the other part of the scripts.

Again this have to be done in runtime since the DB container has not been linked during the Build phase