-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Environment variables should be capitalized #21021
Comments
Hey adityapatadia, thanks for raising the issue. |
I meant any config that can be set with ENV variable. Take this example |
Got it, thank you for clarifying! |
I would consider this a bug in Doppler rather than Ghost. While it's a convention that env vars are upper case, it's not a requirement.
And this assertion is false. No common shells or tools have a problem with env vars not being upper case. The format of Ghost environment variables serve a specific purpose to map exactly to the names of valid values in Ghost's config file. There is already complexity in the system by supporting both the JSON config configuration and the environment variables that match exactly. Supporting another format of environment variables adds unnecessary complexity. I suggest filing a bug with Doppler instead. They are failing to support valid environment variables. |
It's really impossible to set JSON config in container environments. ENV variables are the only option. Anyway it's a request to consider this. |
@adityapatadia
|
Sounds like a good idea but problem is doppler injects variables on |
Hello @adityapatadia i would like to work upon this issue.Please assign it to me. |
Issue Summary
When using secrets manager like https://www.doppler.com/ the ENV variables are always enforced to be uppercase. It's always best practice to uppercase env variables to ensure compatibility across different shells.
Steps to Reproduce
Try to set uppercase env variable and it does not work.
Ghost Version
5.94
Node.js Version
20
How did you install Ghost?
Docker
Database type
MySQL 8
Browser & OS version
No response
Relevant log / error output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: