It would be generally nice to have the freedom to decide if a specific service should be accessible under a subdomain or a specified path. Specifically, we want to be able to distinguish between an item, its webpage and its machine-readable representation in a linked data fashion:
In Linked Data, each item of interest is given a URI, that in turn redirects to
either human-readable HTML or machine-readable RDF depending on content negotiation.
For this is would be desirable to serve the UI under a www. subdomain.
We should therefore check that each outside-facing Renku component can made accessible in both ways.
In other discussions it has been decided to keep the UI URL as the basic renku domain URL and instead map the other services elsewhere. Is this issue still needed and is it still blocking #676?
676 has been closed, so this issue is not a blocker anymore. However, I think it would still be nice if we were able to decide the URL (prefix or subdomain) for each exposed service individually.
It would be generally nice to have the freedom to decide if a specific service should be accessible under a subdomain or a specified path. Specifically, we want to be able to distinguish between an item, its webpage and its machine-readable representation in a linked data fashion:
For this is would be desirable to serve the UI under a
www.
subdomain.We should therefore check that each outside-facing Renku component can made accessible in both ways.