mirror of
https://github.com/dehydrated-io/dehydrated.git
synced 2026-01-13 15:13:33 +01:00
What is the relationship between this repo and certbot? #138
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @alexlenail on GitHub (Aug 15, 2016).
@lukas2511 It seems like this repo doesn't depend on certbot at all. Do they do the same thing? Do they do very different things? (Sorry I'm a noob! It would be nice if certbot were mentioned in the readme though, for fellow noobs)
@EvilJordan commented on GitHub (Aug 18, 2016):
This is a great question. I don't know the definitive answer, but from my experimentation, this repo is more of a manual, stripped-down, essentials version (and works really well). I have been able to create tens of dozens of certs for sites quickly and easily with this repo, and setting up a cron job for auto-renew is dead-simple.
Certbot didn't work for me on my non-standard system, seemed bloated, and I found the documentation to be super-unclear, like it was geared towards total beginners, but even then lacked clarity on what was going on.
@seefood commented on GitHub (Aug 20, 2016):
@EvilJordan is correct. The Let's Encrypt system is using a protocol they call "ACME". Like everything else in computers, there's more than one way to implement it. certbot is the default/reference implementation, this repo is a simpler, clearer tool implementing it all in bash. It may not have all the same features (like setting up a temp webserver on port 80), but all the other important features are there, with a clear way of adding the missing ones with the webhooks.
if the ACME protocol gets an update, both certbot and letsencrypt will get an upgrade, but that's the only relationship between the two :)