Since the script keeps all the old certificates as a backup, the folders can get messy after a while. So I thought, a cleanup command would be useful. When there are a lot of different domains, there would be a lot of files to delete manually, so this command helps by checking, which certificates are used and deletes the other ones.
I was thinking about how to implement it, and I think an automated or implicit cleanup would be against the thought of having backups in case of trouble. So I came up with this extra command, so the cleanup can be started explicitly, when the certificates are working fine.
I was thinking about only deleting expired certificates, but first I wanted to start with this idea, so we can discuss on this basis.
🔄 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/80
**Author:** [@code28](https://github.com/code28)
**Created:** 1/9/2016
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `master`
---
### 📝 Commits (1)
- [`e501673`](https://github.com/dehydrated-io/dehydrated/commit/e5016732e673047ea899b686b634040558b2ed76) Add cleanup command to delete old files
### 📊 Changes
**2 files changed** (+32 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
📝 `letsencrypt.sh` (+31 -0)
</details>
### 📄 Description
Since the script keeps all the old certificates as a backup, the folders can get messy after a while. So I thought, a cleanup command would be useful. When there are a lot of different domains, there would be a lot of files to delete manually, so this command helps by checking, which certificates are used and deletes the other ones.
I was thinking about how to implement it, and I think an automated or implicit cleanup would be against the thought of having backups in case of trouble. So I came up with this extra command, so the cleanup can be started explicitly, when the certificates are working fine.
I was thinking about only deleting expired certificates, but first I wanted to start with this idea, so we can discuss on this basis.
---
<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/80
Author: @code28
Created: 1/9/2016
Status: ❌ Closed
Base:
master← Head:master📝 Commits (1)
e501673Add cleanup command to delete old files📊 Changes
2 files changed (+32 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📝
letsencrypt.sh(+31 -0)📄 Description
Since the script keeps all the old certificates as a backup, the folders can get messy after a while. So I thought, a cleanup command would be useful. When there are a lot of different domains, there would be a lot of files to delete manually, so this command helps by checking, which certificates are used and deletes the other ones.
I was thinking about how to implement it, and I think an automated or implicit cleanup would be against the thought of having backups in case of trouble. So I came up with this extra command, so the cleanup can be started explicitly, when the certificates are working fine.
I was thinking about only deleting expired certificates, but first I wanted to start with this idea, so we can discuss on this basis.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.