Add a new Django app 'demo' that contains the command 'create_demo'
Generate dummy users and files with existing factories.
Signed-off-by: Fabre Florian <ffabre@hybird.org>
In order to be able to test resource server we need to be able
to share a network between our docker compose stack. Let's add
a network to make it work.
in the wopi protocol, a wopi client should expose a discovery url
allowing the host to configure the url to use based on the extension or
the file mimetype. We use now this discovery url to configure the wopi
host and remove all the existing mechanism made in the settings.
We need to adapt the frontend code to use the PUT method to upload a
file instead of the POST method.
The headers used to sign the url must be added to the request sent. For
now the X-ams-acl header is used.
This way of running management command is much quicker as it
runs the commands in existing container instead of starting
a new one. This target is going to be used in the e2e tests to
run fixtures quickly.
We want to be able to quickly start a local isolated env for the
e2e testing, we don't want to share to same db with the classic
dev env because the e2e db should be empty before tests execution.
And we don't want to clear our dev db every time. Also provide a new
makefile handy command to launch the e2e env and the tests in one
command, great.
We had lot of problems with the previous env.d system.
Users were often confused by the need to change
the env.d files manually, leading to issues
when using the project locally.
This commit introduces a new system that uses
.env.local files, which are automatically created
and can be modified by users without affecting
the original env.d files. This should simplify
the development process and reduce confusion by
removing the need to manually edit env.d files.
In order to ease the oboarding of developper or to easily test the whole
application, we remove all services in compose non related to
development mode and the frontend dev container is started with the
`make run` command.