-
Notifications
You must be signed in to change notification settings - Fork 28
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
Tonic support #51
Comments
Any specific ideas on how to do that? I'm not quite sure what would be useful here. Maybe the best way to integrate would be contributing (to tonic) a feature gated method to its high-level server builder, which takes an AcmeConfig, instead of the fixed certificate config they have at the moment. |
Just came across this myself. I've not tried this yet, but after looking at this tonic TLS server example I'm wondering whether you could use a @FlorianUekermann do you think that will work? I'm yet to try it but will do as soon as I can find time. I appreciate this doesn't mean that this crate gets a more convenient tonic integration but assuming it's possible to do the above, I feel like it wouldn't be a stretch to add it, or at least an example. EDIT: I think you'd also have to change the Or it may even be possible to use the tokio integration (https://docs.rs/rustls-acme/latest/rustls_acme/tokio/struct.TokioIncoming.html) like this: https://github.com/FlorianUekermann/rustls-acme/blob/main/examples/high_level_tokio.rs And pass incoming TLS connections straight to |
Yes, both options look very promising. The convenience aspect is more about tower than tonic I guess. You might even be able to use the high-level API then. Given how popular tower is, I think offering helpers for it may be a good idea anyway. |
I see there is Warp and Axum support.
It would be awesome to get Tonic support too
The text was updated successfully, but these errors were encountered: