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
Deploying the Aerie UI to a non-standard path (e.g., /aerie) requires modifying the code and rebuilding the image.
Describe the feature request
I need or want [...]We need to host Aerie at a /aerie base path (i.e., https://ourhost/aerie). In order to make the Aerie UI work with the /aerie base path we have to modify svelte.js to hack in the desired base path, and then rebuld the UI package:
sed -i "s#base: \'\'#base: \'/${BASE_PATH}\'#g" svelte.config.js
It would be really nice if this could be configurable without a full rebuild.Right now we have a whole Jenkins pipeline setup just to get around this limitation.
The text was updated successfully, but these errors were encountered:
Noting for completeness the workaround is documented here. It seems the Svelte Kit issue blocking this has been closed. I'll take a look next week to see if this is still a limitation.
Just an update here. I did not see an obvious way to do this so I put in a question to the SK team: sveltejs/kit#10147, will update here with findings.
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
Deploying the Aerie UI to a non-standard path (e.g.,
/aerie
) requires modifying the code and rebuilding the image.Describe the feature request
I need or want [...]We need to host Aerie at a
/aerie
base path (i.e., https://ourhost/aerie). In order to make the Aerie UI work with the/aerie
base path we have to modify svelte.js to hack in the desired base path, and then rebuld the UI package:It would be really nice if this could be configurable without a full rebuild.Right now we have a whole Jenkins pipeline setup just to get around this limitation.
The text was updated successfully, but these errors were encountered: