Burrow .cfg expected rather than .toml
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
If I'm building the Docker image from master on MacOSX, the resulting containers will look into the config folder for a borrow.cfg config file. If I'm building the image on a linux machine, it'll correctly look for and parse the .toml file. It's weird, I agree, so feel free to delete this if you think it's invalid.
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 comparing the Docker image's config-file selection on macOS and Linux, focusing on the config folder and the reported .cfg versus .toml behavior. Reproduce the build on both platforms and confirm that the resulting container consistently discovers and parses the intended configuration file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100