-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overriding "host" to point to alternative binary repository #74
Comments
proof of concept in 21b6559 shows that |
Maybe just Being able to override |
I meant to do something like I can't see how |
Excellent point. |
@mojodna - still seeing this as useful? |
In theory maybe (custom builds), but it's not something I need at this point. |
Thanks! I see this as potentially useful in theory too. Let's re-open when its needed/useful in practice. |
This should be a must. This morning our entire ci system was down because we couldn't download or build a binary needed by a transitive dependency. |
@fmarmar I think this may be supported after #459 However the breakage this morning impacted everyone using node-tar, so not just node-pre-gyp. And an alliterative repository would not have helped since the breakage was do to the inability to unpack the tar: #477 (comment) |
Logging this idea. Not positive its a good idea and I may not move on it, but...
Say you want to support much older linux distros with custom binaries. As a developer of an app that depends on node-pre-gyp packaged modules you might want to keep 99% of what node-pre-gyp provides but just request that binaries be fetched from an alternative endpoint that you maintain. If we were to support this then an
npm config
style override might be possible:npm config set node-pre-gyp_mapnik_host https://node-mapnik-alternative.s3-us-west-1.amazonaws.com
Then instead of
https://node-mapnik.s3-us-west-1.amazonaws.com
being used from https://github.com/mapnik/node-mapnik/blob/c36d90b237e76e013bcd2c2e15d11ad304658a9a/package.json#L13, the alternativehost
would be used:The text was updated successfully, but these errors were encountered: