-
Notifications
You must be signed in to change notification settings - Fork 12
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
[feature] https out of the box? #323
Comments
I'll open up port I would be interested in how you use |
Well, I've been directed here by the amazee team when I asked about how to get pygmy to set an extra subjectAltName field in the self signed certificate you get when using https, so you can trust it on the system and Chrome doesn't complain about it still missing subjectAltName, and you have to re-enable the exception every few days (after each Chrome update?). So, if the haproxy version pygmy-go uses doesn't do that yet, that would be a great addition too! |
The containers are like for like - so it wouldn't support anything new. There's a lot of interesting things that the haproxy container could be doing and I get the feeling it will be updated in the future. I've been rather curious about this mechanism myself so I might go back down the rabbit hole. I'm just getting the tests to pass again and I should be good to submit a PR. Could probably swing a release as well... |
Thanks! re subjectAltName, it turns out the cert is not generated on the fly like I thought, but stored in the amazee haproxy image: So, to get that extra field and make it Chrome friendly, I guess the image should be updated. |
There's so much awesome that can come from updates and changes to that image, but because this project is made to replicate All of that said, you can however provide your own custom image to use instead of |
Release v0.7.0 is now out, I hope it helps you somewhat 👍 |
Using a custom image would be the last resort, but I appreciate the offer to add the option to specify such an image. |
Everything that pygmy-go runs is all in configuration, it passes Docker-native API objects directly to Docker's API. Happy you're using it! If you are curious, I wrote a whole heap of documentation that never got finished that is all still relevant: |
Thanks for releasing v0.7.0! I'm getting some weird stdout when launching it tho:
|
Glad it works! :) I'll have to have a think about this one... it appears too much of the ssh-add logs are coming through. |
Hi,
Pygmy proxies https requests out of the box. It seems like pygmy-go doesn't, unless I missed something?
Thanks
The text was updated successfully, but these errors were encountered: