Task #100
closed
Frontend configuration - support for relative serverUrl
Added by Radek Tomiška over 8 years ago.
Updated about 8 years ago.
Description
serverUrl property in frontend configuration can be absolute url only. We need add support for relative url - this could be used, when frontend runnig on the seme server as backend.
serverUrl property in config was changed from absolute url: "http://localhost:8080/rest/api" to relative: "/rest/api"
- Target version changed from Amethyst to Beryl
- Status changed from New to Resolved
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- % Done changed from 100 to 80
relative url doesnt work anymore. 403 (forbiden) status is returned
- Status changed from Closed to In Progress
- Assignee changed from Martin Karcol to Radek Tomiška
- Status changed from In Progress to Needs feedback
- Assignee changed from Radek Tomiška to Vít Švanda
- % Done changed from 80 to 90
I've made core review, some refactoring. I've fixed problem with whole build and with relative url. Now is possible to use aggregator module with profile 'fullApp':
```
mvn clean install -PfullApp
```
to build whole aplication (BE + FE) deployable to custom Tomcat 8.0.* server url. I've added docs too.
Please make do a code review and test.
- Status changed from Needs feedback to Resolved
- Assignee changed from Vít Švanda to Radek Tomiška
- % Done changed from 90 to 100
It works nicely.
- I successfully builded full application and deploy it on tomcat.
- Application worked without any problems.
- I try change serverUrl in idm/config.js. Change of url worked fine. The change will take effect without rebooting.
- I checked documentation in README.md
- Status changed from Resolved to Closed
Also available in: Atom
PDF
