This is my first coopcloud PR, lmk if there is something glaring :)
* [x] I have deployed and tested my changes
LetsEncrypt challenges pass successfully, wildcard cert retrieved
* [x] I have [updated relevant versions in `abra.sh`](https://docs.coopcloud.tech/maintainers/upgrade/#updating-versions-in-the-abrash)
No relevant versions to update
* [x] I have made my environment variable changes [backwards compatible](https://docs.coopcloud.tech/maintainers/upgrade/#backwards-compatible-environment-variable-changes)
Only added new env vars
* [ ] I have added a [release note entry](https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes)
The guide does not say how to do this
This is my first coopcloud PR, lmk if there is something glaring :)
Ah, I think the LETS_ENCRYPT_DNS_CHALLENGE_* env vars are not needed here actually.
, yes, when using the .env.sample, the way to use porkbun is to
uncomment these two env vars, and put in porkbun in the _PROVIDER var
fill in the porkbun api key, and include the compose.porkbun.yml file
similar to ovh, azure, digitalocean etc.
I copied compose.porkbun.yml from compose.digitalocean.yml which does provide these env vars in the services.app.environment section, but I'm not sure what effect that has. So I'll remove them, to be consistent at least with the ovh compose file.
Ah, I think the LETS_ENCRYPT_DNS_CHALLENGE_* env vars are not needed here actually.
, yes, when using the .env.sample, the way to use porkbun is to
1. uncomment these two env vars, and put in `porkbun` in the _PROVIDER var
2. fill in the porkbun api key, and include the compose.porkbun.yml file
similar to ovh, azure, digitalocean etc.
I copied `compose.porkbun.yml` from `compose.digitalocean.yml` which _does_ provide these env vars in the services.app.environment section, but I'm not sure what effect that has. So I'll remove them, to be consistent at least with the ovh compose file.
decentral1se marked this conversation as resolved
ammaratef45
approved these changes 2026-02-16 08:03:25 +00:00
tested, redeployed with the new secret names and letdebug.net shows green
ah, noted. Renamed secrets to be `pb_(s_)?_api

tested, redeployed with the new secret names and letdebug.net shows green
i opted to re-use the existing instructions for how to integrate with providers, and made it a bit clearer how setting LETS_ENCRYPT_DNS_CHALLENGE_PROVIDER works, Hope that addresses the concern :)
i opted to re-use the existing instructions for how to integrate with providers, and made it a bit clearer how setting LETS_ENCRYPT_DNS_CHALLENGE_PROVIDER works, Hope that addresses the concern :)
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.
LetsEncrypt challenges pass successfully, wildcard cert retrieved
abra.shNo relevant versions to update
Only added new env vars
The guide does not say how to do this
This is my first coopcloud PR, lmk if there is something glaring :)
@@ -0,0 +6,4 @@- PORKBUN_API_KEY_FILE=/run/secrets/porkbun_api_key- PORKBUN_SECRET_API_KEY_FILE=/run/secrets/porkbun_secret_api_key- LETS_ENCRYPT_DNS_CHALLENGE_ENABLED- LETS_ENCRYPT_DNS_CHALLENGE_PROVIDERis this supposed to be ovh or something else? (when uncommented from the env file)
Ah, I think the LETS_ENCRYPT_DNS_CHALLENGE_* env vars are not needed here actually.
, yes, when using the .env.sample, the way to use porkbun is to
porkbunin the _PROVIDER varsimilar to ovh, azure, digitalocean etc.
I copied
compose.porkbun.ymlfromcompose.digitalocean.ymlwhich does provide these env vars in the services.app.environment section, but I'm not sure what effect that has. So I'll remove them, to be consistent at least with the ovh compose file.lgtm but I would wait for the recipe maintainers to take a look before merging
Looking good @moosemower, thanks for the work! And welcome!
@@ -0,0 +13,4 @@secrets:porkbun_api_key:name: ${STACK_NAME}_porkbun_api_key_${SECRET_PORKBUN_API_KEY_VERSION}The only thing I'd worry about here is 👇
ah, noted. Renamed secrets to be `pb_(s_)?_api
tested, redeployed with the new secret names and letdebug.net shows green
1d2de06d5cto39a83bc12539a83bc125toc6bfe41c94LGTM!
@@ -77,2 +77,4 @@#SECRET_AZURE_SECRET_VERSION=v1## Porkbun, https://porkbun.com## To insert your secrets:Can you add a section to the README.md about how to integrate porkbun.com? You could then document there how go insert the secrets
i opted to re-use the existing instructions for how to integrate with providers, and made it a bit clearer how setting LETS_ENCRYPT_DNS_CHALLENGE_PROVIDER works, Hope that addresses the concern :)