C.J. May

Another year, another person interested in this feature :) I'm swamped through Monday but if I get some free time next week I might look into [elk-tls-docker's implementation](https://github.com/swimlane/elk-tls-docker/wiki/Letsencrypt%20Walkthrough) as @wallopthecat...

No longer Monday, but I did not forget about this. It's on my to-do list.

I'm back with some ideas. I've seen some services use a certbot container and mount the volume from that to an nginx container. In this case we could just mount...

I'm back with an idea, and would like some input from repo maintainers on if they think this is a good solution. I have tested a docker-compose setup that uses...

Documentation will also need to be updated because there would be some prerequisite work that would need to be done (setting up DNS and port forwarding so letsencrypt can reach...

It's really up to @sherifabdlnaby if he wants to add to the scope of this project. Anyone is able to deploy the above docker-compose file and add their own nginx...

From the discussion in #35, it sounds like adding third party libraries would be tough to implement. Since [vue-mdc-adapter](https://github.com/stasson/vue-mdc-adapter) has been deprecated over 2 years, what do you think about...

Not sure if this is exactly what I want, but there are some improvements that I had in mind that I could implement as part of this. One is to...

As of a5d3b471fbf4f76941345fe5b9d0c8024eda139e clients submit an arbitrary connection key and are queued until they time out or can be bridged with their counterpart client that has a matching connection key....

As of 5ae24b359f14384e6730b8e91533fea1e433cfc7 the connection key must start with the prefix "#!ConnectionKey_" without the quotes. This drops all client connections that don't contain a valid prefix in the connection key...