GitLab

move the db seeding outside the django container_init script

seeding is now performed by the bootstrap script directly (except called
with --noseed). It consists of two parts:
 - seeding the db: with 3 users (admin@localhost, devel@localhots and
   user@localhost) and one webapp ('sleep' that has 1 version 'latest')
 - seeding the registry with one image: "localhost/sleep:latest" for the
   sleep webapp

Initially the authentication with the registry was performed with a TLS
client certificate installed on the controller.

The registry is now configured to use token-based authentication (to
give access to the users), but unfortunately it cannot be configured to
support multiple auth methods. So we have to provide a token for the
controller.

This is a 'God' token, it gives total access (pull and push) on all
images.

This commit will have to be reverted when we go to production

This commit removes the calls to the 'migration.sh' script that
did a full a import of the rails db (rails apps will be imported
on-demand)

The django db is now initialised from scratch, using the db_seed command

(and have it  generated by the container_init script)

(to store the secret_key)

+ensure that ENV is defined

(rather than everytime the container is run)

(like in the other images)