1. 25 Apr, 2018 1 commit
  2. 24 Apr, 2018 1 commit
    • BERJON Matthieu's avatar
      Complete rewrite of the migration script · 6d81cc40
      BERJON Matthieu authored
      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: BERJON Matthieu's avatarMatthieu Berjon <matthieu.berjon@inria.fr>
  3. 20 Apr, 2018 6 commits
  4. 18 Apr, 2018 5 commits
  5. 17 Apr, 2018 2 commits
  6. 16 Apr, 2018 9 commits
  7. 13 Apr, 2018 5 commits
  8. 12 Apr, 2018 11 commits