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

I renamed a variable to get something more meaningful than "queryset".

I added a method to pass on to the template data related to the webapp.

I renamed the Job views (`JobDelete`, `JobFileDownload`, `JobFileDownloadAll`).
No changes except the class name has been done.

I renamed several URL path for several views to have a coherent naming
convention. I deleted some old code.

Major update of the docstring at every levels (module, classes, methods).
I reordered as well the library calls, deleted a duplicate and replaced the
call to the `User` model by its Django counterpart.

Resolves: #179

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

I added a helper function to extract the job logs for a specific job in the Redis database.
The function is a copy of another part of the code not merged yet in the master branch.

I updated the view accordingly, added a proper docstring and moved the class in the module to keep the code ordered.
I updated as well the template to display the data.

The webapp update call was wrong because of the change of the template
file naming. It's now fixed.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

The call to the runner update template in the view was wrong. I fixed
it. I tool as well the advantage of that fix to hide the command input
(the one used to register a runner on allgo) at the runner creation.
It's now possible to see it only when on the update view.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I created a mixin that check if a user belongs to one or more groups and
raise a `PermissionDenied` error if it's not the case.
I updated the `WebappCreate` view accordingly.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

There was still a bug regarding the template name. I deleted as well the
old unused class view.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

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

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

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

I updated the file name to respect the naming convention.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I changed the template file name to respect the naming convention.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I changed the template file name to respect the naming convention.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I changed the name of the template file to have a kind of naming
convention.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I changed the name of the job creation template (file name changed). I
updated as well the callback names.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the view by changing its class name, the handle for the `url`
template method. I added some javascript to display the name of the
chosen files, update the Form class to adapt the labels. I adapted the
url handles wherever it applies.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the job list by mainly changing the template (adding
pictograms for the status of the job, adding the date).
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the view by changing the route, renaming the class view and
update the templates accordingly.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the runner update view by creating a new route, updating the
view class naming and performing several changes in the templates
(links and breadcrumbs).
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the runner creation view by creating a new route, updating the
view and adapting the template accordingly.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the runner list view by changing its route, updating its view
and some minor modifications into the template, main menu and css
stylesheet.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the user password update view by creating a new route,
changing the class naming and updating the resulting templates.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated this view by changing the route, updating the class naming
convention and make few changes in the template.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the SSH view, created the new route, changed the class naming
convention and update the template accordingly.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the view by fusionning all the data (name, ssh key, token) on
the same page. I renamed the classes to fit the new naming. I changed
the routes.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the sandbox creation by changing to route, update the view
class name to fit the new naming convention. I updated the template
accordingly.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I rewrote the the webapp creation view to satisfy new requirements. I
first changed the route to be coherent with the new routing system. I
changed the view name to be coherent with the new view naming (removing
the `View` as the end of the class name as it's obvious.

I rewrote completely the template for the webapp creation by adding two
panels, one for the basic and mandatory data and another one for the
advanced data.

I added a new button on the webapp list template that display a button
allowing only users in the `inria` group to create applications.

I created a template tag in order to be able to check if a user belongs
to a particular group in the template.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I changed several routes to have a more coherent (but unfinished)
  routing system on the webapps. In doing so I changed the following
  things:

- the main menu has now the `apps`, `runners` and `profile` menu.
`settings` disapear and the `explore` menu is changed in favour of
`browse`
- A route now list publicly the apps for a given author. A given user
uses this route to see his apps and can see specific buttons to update
and delete his apps (works only as registered user).
- A route has been created to update the app, can be accessed only as a
registered user and be owner of it. It replaced the same route that was
before in `settings/myapps/<docker_id>/update`.
- the templates have been updated accordingly.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the template in order to give the relevant command lines to
update the docker container. In order to perform that, I added in the
django settings the `ALLGO_DJANGO_REGISTRY` that is used to connect to
the registry.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

It was painful to change a webapp ownership because error messages
weren't displayed in case of failure or success. Now if the new owner
doesn't exist in the database, the user has an error message asking him
to enter a valid email.
In case of success, the user is redirected to his webapp list with a
success message remembering him to which user he transfered the app.

Resolves: #167

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

Several views had a `login_url` variable specifying the login url in
case of a protected file. This was inherited from the original user
management. I simply deleted them as the login url is defined now in the
general settings of the django application.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

The webapp creation is done in two steps. A first step that writes the
information in the database. Once the controller has created the
sandbox, the user is allowed to push its application on it and create a
new version.

I updated the models in order to satisfy the current state of the rails
database. I transformed the `sandbox_version_id` as a foreign key as
it's supposed to be in the rails `Webapp` model.
I updated the `WebappVersion` model to add the `state` possible choices.

I updated the webapp sandbox form in order to take into account the
`WebappVersion` model and add the related necessary fields.

I updated the `UserWebappListView` view to match the updated model. I
used as well a context object name to get a handle in the template with
a meaningful name.

The `WebappCreateView` now create an object in the database with all the
necessary data.

The `WebappSandboxCreationView` view create the sandbox and update the
Webapp model with the new version that has been committed.

I updated the templates in order to perform several specific actions.
I added a block called `meta` in the base template. The underlying idea
is to be able to supercharge on page basis the meta tags in the head of
the page. It used in the `webapp_creation_form.html` file where the
refresh every 5 seconds the page to read the database in order to know
when the sandbox is in its "running" state. Afterwards the meta tag is
removed to access the sandbox creation form in order to commit a new
version.

Resolves: #170

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

I added several routes to manage the creation of the webapp and its
sandbox.
The system is at the moment incomplete. The current state of the code
let the user create an app that will be saved in the database. The
second stage of creating the webapp into the sandbox isn't ready yet but
the views and routes for it are ready.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I changed the way of listing the files available for download in the job
detail view. I now use glob that doesn't list by default dotfiles.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>