7 ms·
What if you just set up an nginx reverse proxy? gitrepo.mycompany.com/product.git --> reverse proxy to git.mycompany.com/gitrepo/product.git Should be straigh
by frikk 10y ago
What if you just set up an nginx reverse proxy?
gitrepo.mycompany.com/product.git --> reverse proxy to git.mycompany.com/gitrepo/product.git
Should be straight forward in nginx
- ykler 10y agoJust curious since I am not experienced with this stuff, are you talking about a TCP reverse proxy (so it could work with the SSH protocol too)? And would haproxy work equally well to nginx for this?
- ianleeclark 10y agoIf I remember right, nginx doesn't support ssh + http(s) on the same port. I'd be happy to learn this isn't correct, though because my personal server only is allowing http through.
- tomc1985 10y agoGenerally speaking, you cannot bind more than one service to a port on a given interface
- ianleeclark 10y agoYeah, that's the issue i had ran into. I was `listen`ing on 80, but wanted to multiplex ssh+http on the same port and nginx didn't support it.
- thresh 10y agoYou can actually distinguish between those on a single port using http://nginx.org/r/ssl_preread http://nginx.org/r/ssl_preread and some sslh-like checks using e.g. njs.
- tomc1985 10y agoYou bring up a good point -- nginx proxying won't help for connections made over SSH (which is a large portion of our deployment)
- frikk 10y agoGood point. However, I guess recent nginx supports streaming tcp proxy, so maybe it would work. http://nginx.org/en/docs/stream/ngx_stream_proxy_module.html http://nginx.org/en/docs/stream/ngx_stream_proxy_module.html
- bronson 10y agoPresumably this falls afoul of the "without hacking" requirement.