Description
I'm currently deploying Zeppelin for a customer with corporate firewalls and proxies everywhere.
Zeppelin fails at startup because of npm download.
It seems that proxy parameter at system level (http_proxy env variable) is not used when downloading npm.
Essentially, I would like to have a full standalone binary of zeppelin without any additional download at startup.
If this kind of additional download is unavoidable, Zeppelin startup script should at least follow the proxy setting.
Attachments
Issue Links
- blocks
-
ZEPPELIN-2276 Release 0.7.2
- Resolved
- relates to
-
ZEPPELIN-2214 Should provide node / npm / package installation proxy for Helium
- Open
- links to