Static content for proxy repositories

[ochstobi]

Hello,

I wanted to know if it is possible (and useful) for other users (in enterprise environment) to create a static website for the binding.node files.

Use case: It is forbidden to directly download content from github.com. So node-sass fails because the binding.node files can't be downloaded.
Workaround: Download and host every file on a private server. Set the SASS_BINARY_SITE environment variable to that server.
Problem: With every update builds are failing because new binding.node files are not in the private repo.
Solution: So the idea is to proxy it with e.g. an Nexus Proxy repository like it is possible with https://nodejs.org/dist

Best regards

[saper]

I leave this open for others to comment; I don't think it would be very difficult to setup something that checks Github Releases say once a day for a new release and download the binaries to the mirror.

[tuxknight]

May be it is nessary to package all things including binary to on single npm package. When we use npm as a package management system, we may want npm to deal all denpendences, including sass binary.

It's not difficult to setup something to sync from Github release. The problem is, in a private network, you need to setup a proxy of npm and a proxy of github release to run npm builds and it will become a technical debt that we need to maintain this proxy besides npm proxy.

[saper]

@tuxknight a list of all binaries is available for every release. Those are relatively large files and we constantly keep adding more as more platforms and node versions are supported. I think this is too much to put into one binary package.

[xzyfer]

May be it is nessary to package all things including binary to on single npm package

This is not feasible as the resulting package would be well over 100mbs.

If you need a mirror we suggest you copy the binaries to a perferred server as part of your node-sass upgrade process. This is how many enterprise users work. We offer some environment variables to configure where the binaries are downloaded from during npm install. You can find these environment variables towards to end of the README.