Add an ENV_OVERRIDE variable so docker-compose can load an
extra env file (e.g. common.e2e) on top of common.local.
This lets the e2e runner enable WOPI_CLIENTS=collabora
without touching the default dev config.
The backend service was hardcoded to use common.local. We
now use ENV_OVERRIDE to select the env file, consistent with
the postgresql config. This enables e2e tests to use their
own common.e2e env file.
We want to add documentation showing how to use DS_Proxy with Drive.
With proxy is fully optionnal and is here if you want to an encryption
layer between Drive and the object storage.
Search in Drive relies on an external project like "La Suite Find".
We need to declare a common external network in order to connect to
the search app and index our documents.
Signed-off-by: Fabre Florian <ffabre@hybird.org>
We want to migrate our projects from pip to uv to take the benefits of
the lock file and have reproducible installations.
A first uv.lock file is comitted and the Dockerfile and compose are
modified to work with uv
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.
The configure wopi command is ran after the app-dev service is healthy.
To be sure wopi is correctly configured we must ensure both collabora
and onlyoffice are healthy.
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.
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.
Set `sslRequired` to `none` for all realms in the keycloak dev service.
By default this settings is set to `external` and only local IPs are granted
to access to the server without SSL. But sometimes, with docker (desktop?)
it appears the network configuration may keycloak to consider the accessing
ip as not local.
We also took opportunity of this change to use the latest keycloak image version
Resolve#291
The labels used in the item path were incremented from the previous path
used. To do this, we needed to fetch the nearest sibling, increment it
to insert it. This causes race condition, hard move and hard code. We
choose to change it by using the item id as label.
