GitLab

It makes sense to do things in the same way the debian packages have
been setup

A container that starts a cron job to use the backup.sh script

Having such a high value for uwsgi_read_timeout does not make sense for
most requests. Therefore it makes sense to create a new route for
uploading which has its own value for that parameter.

Placing the configuration in the separate file helps prevent
duplication.

keyserver was still set to the old rby server, now it correctly point to
an sks installation on vda.

vidjil log files were being removed by dockre volumes. recreating them
in the uwsgi entrypoint script allows us to ensure they exist

The nginx logs were redirected to stdout and stderr, however we need
them in files in order to display them in the vidjil admin page.

app moved, the repository did not. Until we have decided on a generic
name for the backend server, vda will have to suffice.

The repository address was set to a server-specific address. This one
should always point to the correct server

The initial docker configuration wasn't working correctly, so this was
an opportunity to switch to a docker-compose to manage individual
services.
This allowed to also better fit the docker philosophy of lightweight
containers that manage only a single services and/or process