-
Notifications
You must be signed in to change notification settings - Fork 27
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
Multiple proxy services #49
Comments
Did it myself - #50 |
Ping @hamburml |
Thanks for the PR and the issue. I don't use Docker Flow anymore and I don't have a setup to test this PR. The changes look right, but I can't be sure that certbot api is still the same. Did you test your changes? |
Yes but only manually. I didn’t go through any testing suite. I have been using it in one of my projects with the changes and they work correctly.
Arseniy Banayev
[email protected]
(407) 462-0998
…________________________________
From: Michael Hamburger <[email protected]>
Sent: Saturday, July 25, 2020 6:20:00 AM
To: hamburml/docker-flow-letsencrypt <[email protected]>
Cc: Arseniy Banayev <[email protected]>; Author <[email protected]>
Subject: Re: [hamburml/docker-flow-letsencrypt] Multiple proxy services (#49)
Thanks for the PR and the issue.
I don't use Docker Flow anymore and I don't have a setup to test this PR. The changes look right, but I can't be sure that certbot api is still the same. Did you test your changes?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#49 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABPDBTZGZQ3M4F6GQWFAEY3R5KWVBANCNFSM4LFJ3UAQ>.
|
I merged it into master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for the wonderful service - I use it in production and it works smoothly.
Docker Flow Proxy supports running multiple independent proxy services (see
PROXY_INSTANCE_NAME
at https://proxy.dockerflow.com/config/). Would it be easy for you to support multiplePROXY_ADDRESS
values?The text was updated successfully, but these errors were encountered: