Open davidediruscio opened 4 years ago
Might be a task relevant to scava-deployment instead...
Hi @mhow2 the api gateway component has been conceived exactly for that purpose. It should be just a matter of properly configuring it by means of the file
Il giorno ven 14 dic 2018 alle ore 11:17 mhow2 notifications@github.com ha scritto:
As mentioned in this thread https://www.eclipse.org/lists/scava-dev/msg00042.html, at some point it would be nice if we provide a normalized way to access the various services by context instead of ports:
Admin UI - https://instance.ltd/admin Prosoul - https://instance.ltd/prosoul APIs - https://instance.ltd/api
Might be implemented as a reverse proxy config...
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/crossminer/scava-deployment/issues/26, or mute the thread https://github.com/notifications/unsubscribe-auth/AB7wEIQWVV9Xk0YlbuuLkLQyNIP03x4_ks5u43qigaJpZM4ZTQCr .
@davidediruscio : here I'm talking about all the public URLs, not especially the APIs which is another layer (to me) : because we would like to have everything served on a single public port, including APIs and various web UIs
We could have https://instance.ltd/api mapped to the API Gateway, then the API Gateway would be able to route https://instance.ltd/api/administration to the good service/endpoint. https://instance.ltd/api/kb to the knowledge base port 8080 Etc.
Yes, good point! Thanks.
As mentioned in this thread, at some point it would be nice if we provide a normalized way to access the various services by context instead of ports:
Admin UI - https://instance.ltd/admin Prosoul - https://instance.ltd/prosoul APIs - https://instance.ltd/api
Might be implemented as a reverse proxy config...