-
Notifications
You must be signed in to change notification settings - Fork 197
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
ACME integration #686
Comments
This issue should be closed:
|
I've left the company and stopped contributing regularly to this project 2 years ago, so sorry if my issue triaging has not been great lately. |
On Sat, Aug 05, 2023 at 10:24:39AM -0700, Geoffroy Couprie wrote:
Why do you feel it is draining here?
It emmits "zero fuck given" or in less harsh words
"we don't care about it, neither should you do"
Are you looking to contribute to this project? If yes, it might be
best to start by the docs and try to run it,
Work in progress, part of it is checking open issues ;-)
and contact the developers directly,
because the issues are heavily influenced by Clever Cloud's internal roadmap
Acknowledge. FWIW I tent to aim for win/win.
... stopped contributing regularly to this project ...
Another reason for closing this issue.
Groeten
Geert Stappers
--
Silence is hard to parse
|
Hello @stappersg, |
This issue is indeed superseded by #926 |
there's an external tool called sozu-acme that can set up certificates in sozu. It works well but must be run manually.
Now that sozu has a better futures executor in the main process, I'd like to integrate more tasks like this.
For large deployments like we do at Clever Cloud, this would be deactivated (because certificates would better be managed centrally instead of in every load balancer), but for smaller architectures, I'd like to have sozu automatically set up certificates and HTTP->HTTPS redirections, to make the easy path safer
The text was updated successfully, but these errors were encountered: