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

Further cleaning & integration in the django container

See merge request !28

I forgot to update the path to the SQL file to apply the migration after
the table creation.

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

The current process to migrate the data suffers from side effects,
especially when the database needs to drop, start from scratch and add
some migrations through Django. Django handles really badly an existing
database and it's impossible to reproduce a migration process from
scratch when django migrations had been add up to the current database
migration process.

This commit resolve this by reversing the process from migrating to old
database to the new one and telling django to take this new database as
it is to telling Django to create the database from his models and
then inserting the data into the new database. By doing so, any
migration applied through Django is taken into account at any stage
during the process.

During the rewriting of the migration process I discovered several
issues that needed to be addressed.

- deletion of the token management library
- add of a token field in the allgo user table
- add of foreignkeys instead of onetoone fiels in the webapp to avoid a
uniqueness issue on fields that were supposed to have several times the
same ID.
- Update of the default values of job's fields

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

I updated the view and template in order to be able to regenerate a
token if the user needs to do so.

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

I added an attribute to the form to make him read only. Now just the
"generate" button needs to be handled properly and find a way to display
the value of they token key into the field.

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

I Updated the user form view and created two new views for the ssh key
and token. The current token view doesn't work properly and needs to be
handled in a better way. It shouldn't be a proper form anyway, just a
button to generate a new token if necessary.

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

I added the creation of a token at the user creation.

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

I added the authentication using basic tokens that corresponds to the
current API.

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

I updated the API in order to manage jobs.
Now the GET and POST http commands are available to select and create
jobs for a given user (on `jobs/` endpoint).
The GET and DELETE http commands are available to select a given job for
a given user on `jobs/<id>` endpoint.

I updated the `settings.py` file I added two variables to have
informations related to the datastore directory and the directory name
that will host the jobs files. The current setup is
`/vol/rw/datastore/jobs/<job_id>`.

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

The script is now well-structured (with functions!) and can be used
to reset a single container, without requiring a bootstrap of the
whole environment.

    usage: $0 [CONTAINER ...]

    The bootstrap script initialises the environment and the selected
    containers (or by default all the containers).

    If a container is already initialised, then the script asks for
    confirmation before purging its data (to bootstrap it again).

This commit also merges the 'prepare.sh' and 'init-container' scripts
into 'bootstrap'.

(to store the secret_key)

mysql-client is needed because the import script uses mysqldump

(thus we'll have security updates)

- install django statics into /var/www at image build time
- django now on port 8000 (django's default) instead of 4000
- rename @allgo as @Django in nginx's config to decrease confusion
- publish port 8080 in docker-compose

- django is now launch in the foregroud, and its stdout/stderr is now
  the container stdout/stderr

- nginx is now run as a background process, without supervision. A
  HEALTHCHECK CMD is added to monitor the status of nginx (so as to
  a nagios alert in case an hypothetical nginx crash)

- add ALLGO_HTTP_SERVER to select the http server. Default is
 'gunicorn', docker-compose.yml sets it to 'django' for development.

and define them in config.env with a default value

it is unused and cause extra delayed when loading the page
(because they load some files from the cloud, which does not
 respond very well)

- env variables are defined in 'config/env.py', this includes:
  - their default value
  - their documentation

- the loaded variables are stored as attributes of this module
  (eg: config.env.ALLGO_DEBUG)

- all variables are guaranteed to be set once the module is loaded
  thus, the config.settings just has to use env.ALLGO_XXXXX

- the sphinx documentation of the variables is generated directly
  from the source code

- the plumbing is done by the config.env_loader module (while loads
  the variables, and patches the docstring of the config.env module)

It fixes an error in the docker_os model that was inherited from
TimeStamp model but doesn't have the rows `created_at` and `updated_at`.

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

I add a mistake in the name of a python package.

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

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

+ensure that ENV is defined

(to suppress a warning at runtime)

I updated the dockerfile with the correct package for the REST API
framework.

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

I added the logo and updated the README page to give insights on the
font dependencies.

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

Add of jobs API

I added a partial but fonctionning REST API for the jobs management.
It's possible to list jobs according to its username, you can create,
  update and delete a specified job related to its username.

In order to do that I used a new django package called rest_framework.

I had to do minor modifications in the model because of some bugs but it
doesn't have any impact on the current state of the database.

I created a subapp called `v1`for the API to keep track of the versions
and avoid users to have strange behaviours and have time to switch to
the new API version before a full deprecation.

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

I created the job submission using the HTML gui. It still lacks the file
upload.

I updated as well the links in the web app list and detail pages.

I accepted a merge as well coming from Sébastien about the token system
and flatten the urls for a better readibility.

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

my setup seems to require it (did not investigate further, and this
will be void if we switch to nginx+uwsgi)

(rather than everytime the container is run)

it's easier to read and easier to comment