Originally created by @edrozenberg on GitHub (Sep 7, 2022).
My OS (Slackware) uses dehydrated as the default cert tool. Since this tool receives no changes since almost 1 yr ago, and almost no issue comments by the developer since 2020 (there was 1 in 2021), is the project dead?
Asking before putting in the work to set up this tool on a bunch of servers, vs. putting in the work to use acme.sh or some other similar Shell/C/Python tool which is still actively developed. I'm not tracking LetsEnc feature changes closely, but I can imagine that project making changes that might not be supported by a dessicated dehydrated project. Thanks.
Originally created by @edrozenberg on GitHub (Sep 7, 2022).
My OS (Slackware) uses dehydrated as the default cert tool. Since this tool receives no changes since almost 1 yr ago, and almost no issue comments by the developer since 2020 (there was 1 in 2021), is the project dead?
Asking before putting in the work to set up this tool on a bunch of servers, vs. putting in the work to use acme.sh or some other similar Shell/C/Python tool which is still actively developed. I'm not tracking LetsEnc feature changes closely, but I can imagine that project making changes that might not be supported by a dessicated dehydrated project. Thanks.
Dehydrated is certainly not dead. I fix issues as they come along and am working behind the scenes on a major rewrite (which unfortunately is coming along rather slowly). I'm trying to stay up to day with changes to the protocol, which luckily became rather stable so dehydrated also keeps on working without any issues.
@lukas2511 commented on GitHub (Sep 7, 2022):
Dehydrated is certainly not dead. I fix issues as they come along and am working behind the scenes on a major rewrite (which unfortunately is coming along rather slowly). I'm trying to stay up to day with changes to the protocol, which luckily became rather stable so dehydrated also keeps on working without any issues.
That's good to hear, and it's fine as long as the current version continues to work. If a rewrite comes sometime in the future, great - I don't know the historical stats but many rewrites get abandoned before they can deliver. Thanks for this project.
@edrozenberg commented on GitHub (Sep 8, 2022):
That's good to hear, and it's fine as long as the current version continues to work. If a rewrite comes sometime in the future, great - I don't know the historical stats but many rewrites get abandoned before they can deliver. Thanks for this project.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @edrozenberg on GitHub (Sep 7, 2022).
My OS (Slackware) uses dehydrated as the default cert tool. Since this tool receives no changes since almost 1 yr ago, and almost no issue comments by the developer since 2020 (there was 1 in 2021), is the project dead?
Asking before putting in the work to set up this tool on a bunch of servers, vs. putting in the work to use acme.sh or some other similar Shell/C/Python tool which is still actively developed. I'm not tracking LetsEnc feature changes closely, but I can imagine that project making changes that might not be supported by a dessicated dehydrated project. Thanks.
@lukas2511 commented on GitHub (Sep 7, 2022):
Dehydrated is certainly not dead. I fix issues as they come along and am working behind the scenes on a major rewrite (which unfortunately is coming along rather slowly). I'm trying to stay up to day with changes to the protocol, which luckily became rather stable so dehydrated also keeps on working without any issues.
@edrozenberg commented on GitHub (Sep 8, 2022):
That's good to hear, and it's fine as long as the current version continues to work. If a rewrite comes sometime in the future, great - I don't know the historical stats but many rewrites get abandoned before they can deliver. Thanks for this project.