1. 20 Jun, 2018 7 commits
  2. 19 Jun, 2018 1 commit
    • BERJON Matthieu's avatar
      Reading of Redis logs for a specific job · 96741268
      BERJON Matthieu authored
      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.
      96741268
  3. 05 Jun, 2018 3 commits
  4. 04 Jun, 2018 2 commits
  5. 01 Jun, 2018 9 commits
  6. 31 May, 2018 11 commits
  7. 30 May, 2018 2 commits
    • BERJON Matthieu's avatar
      Rewriting of webapp routes · 08dbce4d
      BERJON Matthieu authored
      
      
      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: BERJON Matthieu's avatarMatthieu Berjon <matthieu.berjon@inria.fr>
      08dbce4d
    • BERJON Matthieu's avatar
      Update of the template for docker update instructions · b33958ac
      BERJON Matthieu authored
      
      
      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: BERJON Matthieu's avatarMatthieu Berjon <matthieu.berjon@inria.fr>
      b33958ac
  8. 29 May, 2018 3 commits
    • BERJON Matthieu's avatar
      Change a webapp ownership · c4645d73
      BERJON Matthieu authored
      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: BERJON Matthieu's avatarMatthieu Berjon <matthieu.berjon@inria.fr>
      c4645d73
    • BERJON Matthieu's avatar
      Bug fix: login redirection error · e24de2f5
      BERJON Matthieu authored
      
      
      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: BERJON Matthieu's avatarMatthieu Berjon <matthieu.berjon@inria.fr>
      e24de2f5
    • BERJON Matthieu's avatar
      Webapp creation feature · 1725aeac
      BERJON Matthieu authored
      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: BERJON Matthieu's avatarMatthieu Berjon <matthieu.berjon@inria.fr>
      1725aeac
  9. 22 May, 2018 1 commit
    • BERJON Matthieu's avatar
      Adding of webapp creation routes · 296bad5e
      BERJON Matthieu authored
      
      
      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: BERJON Matthieu's avatarMatthieu Berjon <matthieu.berjon@inria.fr>
      296bad5e
  10. 17 May, 2018 1 commit