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
Currently, all of the landscape app links and sources are absolute paths from the root of the URL. For example, a logo is pulled from /logos/mylogo.svg. This works fine if you are hosting from the root (e.g. https://landscape.cncf.io). However, if a user creates a landscape and attempts to host it from https://my.org/landscape/, the links and source are broken. The logo source would be https://my.org/logos/mylogo.svg, but it sits at https://my.org/landscape/logos/mylogo.svg on the server.
Can you make the links relative to index.html rather than absolute?
The text was updated successfully, but these errors were encountered:
Boojapho
changed the title
Setup links to serve from non-root URL
Setup links and sources to serve from non-root URL
Nov 1, 2022
By setting PROJECT_NAME, you can workaround this limitation. If I set PROJECT_NAME to landscape all of my source/links are generated relative to /landscape/*. We have our staging area at a different path than production, so this still requires us to rebuild the website, to promote to production.
Currently, all of the landscape app links and sources are absolute paths from the root of the URL. For example, a logo is pulled from
/logos/mylogo.svg
. This works fine if you are hosting from the root (e.g.https://landscape.cncf.io
). However, if a user creates a landscape and attempts to host it fromhttps://my.org/landscape/
, the links and source are broken. The logo source would behttps://my.org/logos/mylogo.svg
, but it sits athttps://my.org/landscape/logos/mylogo.svg
on the server.Can you make the links relative to
index.html
rather than absolute?The text was updated successfully, but these errors were encountered: