Endpoint for the data provider (9164)

[PVince81]

So far, when uploading with TUS, the clients receive a Location header that usually points directly to the port 9164

As far as I understand in deployment scenarios where the proxy is used, we'd want to have that one also routed through the proxy.

We could provide an endpoint "/data" and forward it to 9164.

@butonic does that make sense ?

[PVince81]

the default config will also need to be adjusted to make sure the Location header points at the proxy

[PVince81]

it seems that with EOS the port would be 9160 but for OC data it's 9164, so it might need multiple routes ?

[PVince81]

as discussed with @felixboehm, we must provide this to have everything accessible behind a single port

[butonic]

reva has a datagateway service which we are starting with ocis-reva as part of the frontend cmd. Three things need to be configured to have everything routed through a single entrypoint:

1. the storage providers need to be configured to never expose a dedicated storage driver. this can be done by setting REVA_STORAGE_(EOS|HOME|OC)_EXPOSE_DATA_SERVER to false. This will make the reva gateway use the datagateway instead of the dataproviders directly.
2. the reva gateway needs to use the proxy as the frontend url. try setting REVA_FRONTEND_URL to the outside address (host and port) ...

• there may be config problems because the ocs endpoint prefixes REVA_FRONTEND_URL with https:// to construct the ocs.config.host property while the ocis-reva gateway uses REVA_FRONTEND_URL as the datagateway, which expects a url

3. ocis-proxy should proxy /data to the ocis frontend

[PVince81]

as I understand this will be:

-> proxy (port?) -> datagateway (port?) -> OC storage 9164
-> proxy (port?) -> datagateway (port?) -> EOS storage 9160