Offline Install

[oatkiller]

Hello,
I am trying to use the sentry webpack plugin (https://github.com/getsentry/sentry-webpack-plugin) but my build environment is not connected to the Internet. I can manually download the release and provide a location to it in my file system in advance. I see that configuring the CDN location is possible, but how would you feel about having an option to use the release from disk instead of downloading it at all? As things are now, my only option would be to run a temporary HTTP server (like the install script does during testing.) Please advise. Thanks!

[jan-auer]

I think we could add support for file:/// URLs to solve this, despite some concerns here: node-fetch/node-fetch#75.

However, I assume you are hosting Sentry somewhere in your infrastructure. Wouldn't it be easier to just put the binary there?

[oatkiller]

@jan-auer Thank you very much for the reply. We do have artifactory which we use to host yum, npm and other package management repositories. I'm not sure how I would use artifactory to make the sentry CLI binary available. If I found a way to do so, I would need to make sure that the correct URL pattern is supported. I've pasted a snippet from the docs to help explain what I mean:

By default, this package will download sentry-cli from releases. This should work fine for most people. If you are experiencing issues with downloading from GitHub, you may need to use a different download mirror. To use a custom CDN, set the npm config property sentrycli_cdnurl. The downloader will append "/<version>/sentry-cli-<dist>".

In the mean time, I have worked around this issue by keeping the linux CLI binary in my git repo and spawning a temporary HTTP server while running yarn install. I got the idea from the tests here:

sentry-cli/scripts/install.js

Line 123 in dd12772

if (process.env.SENTRYCLI_LOCAL_CDNURL) {

[tonyo]

We partially addressed the issue in #425
Starting from the next version binaries will be cached in ~/.npm/sentry-cli.
Probably this is not ideal for your specific use case, but at least it opens some room for automation.