-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: use relative URL for 302 redirect [skip ci] #263
Conversation
Small tweak for the nginx+vouch single server example: - use a relative URL for the redirect to vouch's login page
thanks @bgehman ! |
Appreciate it @bnfinet Took me a couple of days, but now I have our little webservice nicely tucked into a kubernetes deployment (along with this "all-in-one" nginx container, and a vouch-proxy container) successfully authn'ing against my corp's github enterprise. Very nice tool you have here. Appreciate all the effort that went in to creating it 👏 |
Thanks for the kind words @bgehman If you ever cared to do a write-up on your setup please do reach out, I'd love to help you document your setup. I'm looking for blog posts for the vouch.github.io launch. Happy to link to your blog from there if you preferred. And please be sure to 🌟 the repo :) |
@bnfinet , here's a quick writeup. We have a documentation server, that basically clones all the repos in our Enterprise Github organizations, and it serves up the godoc for our in-house Golang libraries. It periodically does Goal was to host our go-doc's, on the public internet, but protect access to it to people who can authenticate with our company's enterprise github -- which is also on the public internet. vouch-proxy is the solution! Everything else we do in house is dockerized, and hosted in Kubernetes, hence that is the hosting target for us. Helm
nginx
vouch-proxy Here is some ASCII-art FTW:
|
FTW indeed! cheers @bgehman that's really great |
fix: use relative URL for 302 redirect [skip ci]
Small tweak for the nginx+vouch single server example: