d24e531 bugfix: PRIVATE_KEY is now configurable in config.sh, don't alter this variable after set_defaults()
📊 Changes
1 file changed (+0 additions, -1 deletions)
View changed files
📝letsencrypt.sh (+0 -1)
📄 Description
When overriding PRIVATE_KEY in config.sh, letsencrypt.sh erroneously changes it back to "${BASEDIR}/private_key.pem"
🔄 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/44
**Author:** [@digint](https://github.com/digint)
**Created:** 12/14/2015
**Status:** ✅ Merged
**Merged:** 12/14/2015
**Merged by:** [@lukas2511](https://github.com/lukas2511)
**Base:** `master` ← **Head:** `bugfix_config_private_key`
---
### 📝 Commits (1)
- [`d24e531`](https://github.com/dehydrated-io/dehydrated/commit/d24e531afbd79beff56977f61d9452f95bddf6d8) bugfix: PRIVATE_KEY is now configurable in config.sh, don't alter this variable after set_defaults()
### 📊 Changes
**1 file changed** (+0 additions, -1 deletions)
<details>
<summary>View changed files</summary>
📝 `letsencrypt.sh` (+0 -1)
</details>
### 📄 Description
When overriding PRIVATE_KEY in config.sh, letsencrypt.sh erroneously changes it back to "${BASEDIR}/private_key.pem"
---
<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/44
Author: @digint
Created: 12/14/2015
Status: ✅ Merged
Merged: 12/14/2015
Merged by: @lukas2511
Base:
master← Head:bugfix_config_private_key📝 Commits (1)
d24e531bugfix: PRIVATE_KEY is now configurable in config.sh, don't alter this variable after set_defaults()📊 Changes
1 file changed (+0 additions, -1 deletions)
View changed files
📝
letsencrypt.sh(+0 -1)📄 Description
When overriding PRIVATE_KEY in config.sh, letsencrypt.sh erroneously changes it back to "${BASEDIR}/private_key.pem"
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.