letsencrypt / letsencrypt/pebble
Please support running in the background after opening listening port
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 787
- Forks
- 176
- PR merge metrics
- No merged PRs in 30d
Description
pebble and pebble-challtestserv run in the foreground, and have to be explicitly placed in the background. Please consider adding an option to open a listening port and then go into the background, which would allow a race-free way to start the server and then start making requests to the server, for CI purposes.
Contributor guide
No contributing guide indexed for this repository
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 with the pebble and pebble-challtestserv entry points and trace how each opens its listening port and remains in the foreground. Determine how an option should control backgrounding after the port is ready, and identify the existing CI or server-startup tests to update or add. Done means both servers can signal readiness without a startup race when used in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100