Since we can't trigger a run at some point in the future, this is implemented according to the alternative approach.
It assumes the script is run once per day, so if the randomized renewal time is within the next 24h, a renewal will be triggered.
I did not test this on OSX/non-coreutils systems, so I do not know if the date-magic for it works. But I also didn't find any good portable way to deal with those rfc3339 dates.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/dehydrated-io/dehydrated/pull/959
**Author:** [@BtbN](https://github.com/BtbN)
**Created:** 2/11/2025
**Status:** 🔄 Open
**Base:** `master` ← **Head:** `ari`
---
### 📝 Commits (1)
- [`d53c6df`](https://github.com/dehydrated-io/dehydrated/commit/d53c6df4f7706e2790450ac724c5cb985eb700eb) Implement ARI support when checking certificate renewal
### 📊 Changes
**1 file changed** (+47 additions, -1 deletions)
<details>
<summary>View changed files</summary>
📝 `dehydrated` (+47 -1)
</details>
### 📄 Description
This implements ACME ARI according to https://letsencrypt.org/2024/04/25/guide-to-integrating-ari-into-existing-acme-clients/
Since we can't trigger a run at some point in the future, this is implemented according to the alternative approach.
It assumes the script is run once per day, so if the randomized renewal time is within the next 24h, a renewal will be triggered.
I did not test this on OSX/non-coreutils systems, so I do not know if the date-magic for it works. But I also didn't find any good portable way to deal with those rfc3339 dates.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
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.
📋 Pull Request Information
Original PR: https://github.com/dehydrated-io/dehydrated/pull/959
Author: @BtbN
Created: 2/11/2025
Status: 🔄 Open
Base:
master← Head:ari📝 Commits (1)
d53c6dfImplement ARI support when checking certificate renewal📊 Changes
1 file changed (+47 additions, -1 deletions)
View changed files
📝
dehydrated(+47 -1)📄 Description
This implements ACME ARI according to https://letsencrypt.org/2024/04/25/guide-to-integrating-ari-into-existing-acme-clients/
Since we can't trigger a run at some point in the future, this is implemented according to the alternative approach.
It assumes the script is run once per day, so if the randomized renewal time is within the next 24h, a renewal will be triggered.
I did not test this on OSX/non-coreutils systems, so I do not know if the date-magic for it works. But I also didn't find any good portable way to deal with those rfc3339 dates.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.