GitLab

handle webapp version selection in the job views

Closes #180

See merge request !49

An error was raise when creating a job related to `Exception Value: type
object 'WebappVersion' has no attribute 'COMMITTED'`. The issue was the
misspelling in the model (missing a 't' at "committed"). This commit fix
this issue.

Resolves: #180

Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

mentionned by !41

Registry integration

See merge request !42

manage the evaluation of permissions in the model

See merge request !41

fix docker image name comparison

See merge request !40

registry integration with the reverse-proxy

See merge request !37

(so that a default registry configuration is provided with the image)

(and have it  generated by the container_init script)

`docker_name` is *not* the same as `name.lower()`

migrations are now in the sources
(and the sources are read-only in production anyway)

no longer needed

no longer needed because registry and django are now share the same
host name

- images manifest push/pull are routed through the django server
- all other endpoints are routed directly to the registry


On client-side the registry url is the is the same as the allgo server.
The backend registry location is configured by the
ALLGO_REGISTRY_PRIVATE_URL which is set to "http://{ENV}-registry"
by default (i.e. 'http://dev-registry' in dev)


Because the registry URL is configured at runtime (by the env
var), the nginx config can no longer be static.
/etc/nginc/conf.d/allgo.conf is generated at runtime
 (after loading the django config)

now the server root is routed directly to the django container

This makes the config simpler, now that the reverse-proxy is required
(because of the image push/pull endpoint routed through django)

Manifest push/pull are expected to be routed through the django server
which forwards them to the real registry.

This allows:
- (before push) ensuring there is no commit/push in progress on the
  controller side, and refuse the request until the commit is done
- (after push) ensure that the image is transactionally inserted into
  the db before the '201 Created' response is forwarded to the user

JWT Token authentification

See merge request !32

fixes for the jwt branch

See merge request !36

(must match the exact string)

(not comfortable with that)

(well i guess that the docker client translates the 'null' value into
an empty list, but this behaviour is not specified in the api)

(i am not confortable with undefined behaviours in security-related code)