You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to deploy the latest Prez v4 release in our triply-Dockerised environment (Prez / PrezUI / Fuseki are split amongst 3 distinct containers, each of them having their respective distinct URL) we have noticed URL rewriting issues.
Specifically, the PrezUI docs endpoint is unable to produce its Swagger page that seems to be handled by Uvicorn (hence Prez), because the openapi.json is missing from the PrezUI SPA, and accessible only when hardcoding its URL to the Prez container, within generated .js resources. Similarly, the SPARQL page seems to send its requests to the Prez container when it should should rather direct them towards the Fuseki container.
Is it possible to define, e.g. with additional env variables, absolute URLs instead of the VITE_API_BASE_URL and VITE_BASE_URL pair that seems unable to handle containerisation (is this the "LOCAL_DEV_ENVIRONMENT" comment's meaning?)
The text was updated successfully, but these errors were encountered:
Hi all,
When attempting to deploy the latest Prez v4 release in our triply-Dockerised environment (Prez / PrezUI / Fuseki are split amongst 3 distinct containers, each of them having their respective distinct URL) we have noticed URL rewriting issues.
Specifically, the PrezUI docs endpoint is unable to produce its Swagger page that seems to be handled by Uvicorn (hence Prez), because the openapi.json is missing from the PrezUI SPA, and accessible only when hardcoding its URL to the Prez container, within generated .js resources. Similarly, the SPARQL page seems to send its requests to the Prez container when it should should rather direct them towards the Fuseki container.
Is it possible to define, e.g. with additional env variables, absolute URLs instead of the VITE_API_BASE_URL and VITE_BASE_URL pair that seems unable to handle containerisation (is this the "LOCAL_DEV_ENVIRONMENT" comment's meaning?)
The text was updated successfully, but these errors were encountered: