ConfigHubPub / ConfigHubPub/ConfigHubPlatform
Support writing logs to /dev/stdout in docker
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 80
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
When deploying this with Docker (in our case via Kubernetes), the logs would be better output to /dev/stdout. Unfortunately LOG_PATH does not let us set a file, only a directory.
We've worked around this by messing with the command and symlinking /dev/stdout to /tmp/configHub.log, but it isn't an ideal situation.
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 locating the LOG_PATH handling and the Docker deployment configuration. Check how the current directory-based setting reaches the log file, then run the application in a container with /dev/stdout configured and verify that logs appear through the container or Kubernetes logging stream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript, kubernetes
- Domain
- devops, infrastructure, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100