[ERM-1235] Honor -Dport setting Created: 10/Nov/20 Updated: 23/Nov/20 Resolved: 23/Nov/20 |
|
| Status: | Closed |
| Project: | ERM Platform |
| Components: | mod-agreements |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Johannes Drexl | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Development Team: | None | ||||||||
| Description |
|
mod-agreements: Not being able to set a port for the java process to bind to is breaking any deployment not based on containers. Please change that - it's bad behavior for a software to only bind to a predefined (and even standardized alternative HTTP) port. |
| Comments |
| Comment by Ian Ibbotson (Use this one) [ 23/Nov/20 ] |
|
Agreements (and Licenses and RS ad directory) are spring boot apps and should understand -Dserver.port=X if not, please raise an issue. Spring boot also supports environment variables, fuzzy conversion env SERVER_PORT=1234 and a whole host of other conventions that will probably outlast okapi. |