GitLab

(to be regenerated before the first deployment in production)

I stopped tracking the migrations because at the moment we don't need to
because start from a fresh installation not deployed.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I renamed the poc module into main for clarity.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I stopped tracking the migration files because we changed the migration
system by using an SQL migration file. At the moment only the initial
migration is done on Django, no particular improvements build on the top
of it are necessary at the moment.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

In order to follow good practices for a Django app development I
reorganized the tree.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

To keep track of the migrations, I save the current status of the first
one. It differ in the last one because the migration process doesn't
rely on this initial django migration file anymore but on a plain SQL
script.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the Django migration file to force the order of the fields in
order to match the ones generated by the rails app.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the Django migration file to force the order of the fields in
order to match the ones generated by the rails app.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I reorded the migration file in order to fit the models and have
something easier to read and compare. I didn't have to do any particular
modification as the Django model is identical to the rails one.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the Django migration file to force the order of the fields
generated in the rails database.

The migration generate an error on this particular migration for an
unknown reason although the migration finishes correctly.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I reordered the Django migration file to match the model and easier to
follow for changes.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the Django migration file to force the order of the fields
generated in the rails database.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the Django migration file in order to force the order of the
fields and match the order given by the rails database.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the Django migration file to force the order of the fields
generated in the database.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I updated the docker_os table migration file in Django in order to force
the order of some fields to match the order of the database in rails. I
need to do that for all the tables.
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>

I added the legacy database model into the app.

In order to do that I:

- created the urls.py and views.py file (required by Django)
- created the legacy model using the inspectdb tools given by Django and
stored in models.py
- followed the process to initialize the migrations at the stage of the
model (resulting in the creation of the migrations folder)
Signed-off-by: Matthieu Berjon <matthieu.berjon@inria.fr>