Ability to dynamically set port number at runtime

CSP Request Details

None

CSP Rejection Details

None

CSP Approved

None

Description

Request to update mod-reporting to accept an environment variable (such as GO_PORT) at runtime which would allow for dynamically setting port number (currently set at 12369)

Having this ability will allow setting module port to work with existing pipelines




Environment

None

Potential Workaround

None

Checklist

hide

Activity

Show:

Mike Taylor March 5, 2025 at 12:14 PM

Fixed in .

Mike Taylor March 4, 2025 at 9:41 PM

The discussion at is converging on the answer that the SERVER_PORT environment variable is the closest thing we have to a language-independent standard, so that's what I’ll implement for mod-reporting.

Mike Taylor March 4, 2025 at 3:08 PM

(I am ashamed to say that mod-graphql is hardwired to run on port 3001, and that's the end of it.)

Wayne Schneider March 4, 2025 at 2:59 PM

There is not a standard way, AFAIK. RMB/Vert.x modules use different conventions than Spring, and I don’t recall if mod-graphql (node) has a convention.

I think it would be worthwhile to propose a conventional environment variable on the #development Slack channel and see if we can get some traction with it. Of course that would slow things down for this particular issue, but might be worth it? And it would take some time to implement across all modules.

I’ve raised the question.

Mike Taylor March 4, 2025 at 9:32 AM

OK, thanks . It does seem odd that there is (it seems) no established standard way of doing this for FOLIO modules. But, again, I’ll wait for or to chip in before leaping in and implementing something.

Done

Details

Assignee

Reporter

Priority

Sprint

Development Team

Thor

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created March 3, 2025 at 6:19 PM
Updated March 5, 2025 at 12:14 PM
Resolved March 5, 2025 at 12:14 PM
TestRail: Cases
TestRail: Runs