-
Notifications
You must be signed in to change notification settings - Fork 56
Install kappa behind a corporate proxy #48
Comments
I'm running into the same issue. Have you had any luck since you wrote this? |
Hmm, so kappa uses hapi's built in Also, it looks like @tlivings started investigating this at some point. |
The issue is because reply.proxy can not take custom agents, where a custom agent would be necessary to handle the proxy step. I'm in the process of opening a PR against Hapi to resolve this. The alternative is to implement it ourselves and not use reply.proxy. |
either way, this is pretty important for kappa. I'll defer to you @tlivings for the best approach, but for now I guess let's see if we get any traction with hapi. |
I have submitted a pull request on hapi to allow for an agent to be passed into the reply.proxy handler. If this gets pulled in, the version of hapi kappa depends on would need to be bumped (currently hapi is at 6.5.0) to use it. |
Kappa has been upgrade to use Hapi 6. We should be ready to work against this change now. |
Any news on this? Struggling to set this up behind corporate proxy. |
I thought there was a PR to support custom agents (as noted above). We should definitely look back into this. cc @jasisk |
Any update on this? |
bump. Is there any plan to support this feature? |
Is there any way to install kappa behind a corporate proxy ?
I sucessfully installed kappa with only one declared
paths
to my local couchdb instance (tested commands :npm {adduser, search, test, publish, install}
), butnpm install XXX
fails (freeze) if I addhttp://registry.npmjs.org/
as a secondpaths
to the kappa configuration file.I also tried to run kappa with some options without more success :
The text was updated successfully, but these errors were encountered: