Requiring per-package env variables PACKAGE_NAME_binary_host_mirror makes hosting requisites of multiple packages in a single artifactory difficult
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
* Having a single `binary_host_mirror` variable pointing to a root for binaries of different packages would simplify the use of a local artifactory.
* bcrypt, up to and including the latest version 3.0.0 (but not the one in master), will erase the URL path in the `bcrypt_lib_binary_host_mirror` variable because its `remote_path` started with a forward slash.
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 tracing how package-specific binary_host_mirror variables and remote_path values are handled. Done means a single root mirror can host binaries for multiple packages, while bcrypt URLs retain their existing path instead of losing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100