mirror of
https://github.com/pocket-id/pocket-id.git
synced 2025-12-11 07:42:58 +03:00
🚀 Feature: Configure SMTP via Environment Variables #401
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 @userbradley on GitHub.
Feature description
Ability to configure SMTP config via Environment variables
Pitch
It would be nice to be able to set the SMTP configuration from environment variables
Something like the below
SMTP_HOSTSMTP_PORTSMTP_USERSMTP_PASSWORDSMTP_TLSSMTP_SKIP_CERT_VALIDATIONMy use case comes as I am running this in Kubernetes, and I'd like to get as much config out the way in code as possible before logging in for the first time etc, also allows me to seamlessly rotate secrets in my secret manager of choice when it just restarts the pod when a k8s secret changes
@userbradley commented on GitHub:
Yes I agree. I opened this issue whilst confirming SMTP haha!
But yes, I think being able to supply a yaml file or env variables would be preferable for all app settings
@stonith404 commented on GitHub:
I believe it’s more logical to allow all “Application Settings” to be defined via environment variables, rather than limiting this flexibility solely to SMTP configuration.
@stonith404 commented on GitHub:
This has been released in
v0.31.0. For more information check out the docs.@kmendell commented on GitHub:
I was exploring how other applications do this, and its seems like if a env variable is defined it will be prioritized over the UI, and then that can not be edited via the UI if set in a env variable or on next restart the env value will replace whatever was set in the UI, does this sound like a solid approach for this?