You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.
I am interested in taking control of this. I may take me a while to do the work but I have the time. I also have experience dealing with TLS certificates and the related infrastructure (mainly openssl) which is probably the hard part here. My motivation would be that I need something like this for a file server I am writing, so this is just good timing.
I think the first step would be taking the letsencrypt.rs module and pulling it out into it's own repo. Once that's done I'll very hapilly delete the code here and your repo can be the home for future development!
Does that make sense? Is there anything I could do to make the transition smoother?
Sounds great!
On Jun 5, 2017 12:52 PM, "Alexander Addy" <notifications@github.com> wrote:
Seems pretty straightforward. I'll be able to start this Thursday at the
latest and will comment here with the repo once I have something to look at.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#8 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAADBIVkGxxPt3m3HSuCrCrCfF26bz7pks5sBDJCgaJpZM4NaMvb>
.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
No description provided.
The text was updated successfully, but these errors were encountered: