In feature/commons branch, the UI currently makes API calls using a fully qualified urls, where the base of the url comes from the UI's node.js server.
The UI should just use relative urls, which will be resolved relative to the host the UI is running on.
To get this working when running the UI locally, the UI can take advantage of the proxy feature in Angular CLI.
Doing this will a step towards getting rid of the UI's node.js server, and will also enable the UI to be deployed on s3/CDN.
┆Issue is synchronized with this JIRA Story
┆Project Name: Boardwalk-UI
┆Issue Number: BOARD-54
┆Epic: Google authn for Boardwalk
NoopDog
commented
6 years ago
In feature/commons branch, the UI currently makes API calls using a fully qualified urls, where the base of the url comes from the UI's node.js server.
The UI should just use relative urls, which will be resolved relative to the host the UI is running on.
To get this working when running the UI locally, the UI can take advantage of the proxy feature in Angular CLI.
Doing this will a step towards getting rid of the UI's node.js server, and will also enable the UI to be deployed on s3/CDN.
┆Issue is synchronized with this JIRA Story ┆Project Name: Boardwalk-UI ┆Issue Number: BOARD-54 ┆Epic: Google authn for Boardwalk