spring-projects / spring-projects/spring-boot
Find a way to support PORTFILE (or equivalent) but for non-web apps
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
In https://github.com/spring-projects-experimental/spring-boot-testjars/issues/80 we have been discussing this. Testjars relies on the app it is running to be a Spring Boot webserver. It then switches on the WebServerPortFileWriter and watches the PORTFILE to read the port of the running application. This is neat, but it doesn't work if the app is not a web-server (MVC or webflux essentially). Maybe the PORTFILE could be generalized in Boot so that other listeners could be activated in a similar fashion? Or maybe there's a better way.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the WebServerPortFileWriter behavior described in the issue and the linked spring-boot-testjars discussion. Determine how a PORTFILE or equivalent could expose information for non-web applications and which listeners would need activation. Done means there is an agreed design that supports non-web apps without relying on an MVC or WebFlux web server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100