letsencrypt / letsencrypt/pebble
Unable to set httpPort and tlsPort without a config file
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 787
- Forks
- 176
- PR merge metrics
- No merged PRs in 30d
Description
I think it would be nice if more options could be set through command line arguments or through environment variables. In my case, I would like to set httpPort and tlsPort to regular values: with Docker image it is easy to do have them on regular ports. But doing that seems to be hard when running Pebble on GitLab CI as Docker runs as a separate Docker-in-Docker container, so it is hard to get a config file in there to bind mount it into the container to set a config file. The only way I found is that I do another Pebble image, extending official one, with my own config file and then use that one. A lot of work just to change two settings.
I have had great experience with Kong for CLI and config parsing in Go.
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 by reviewing Pebble's existing configuration loading and command-line startup flow, then trace how httpPort and tlsPort are currently read from the config file. Define the desired command-line and environment-variable behavior, including precedence, and verify that both ports can be set without mounting a config file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100