Explain removal of environment variables DEFAULT_EMAIL
and DEFAULT_PASSWORD
#3242
-
The docs are somewhat contradicting regarding docker compose setup with environment variables; the "installation checklist" states that you need to set After looking through the history, I saw The reason in #2722 states:
I've passed those environment variables to the container, but that didn't do anything, so I guess they are completely removed now, which brings me to my question: Isn't it possible to allow custom email/password for initial setup and just fallback to default email/password if those environment variables are empty? I don't understand why the functionality was removed completely as the ability to supply your own email/password makes it easier (and more secure) to setup the container without manual intervention. Docker: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
As you've noted, that environment variable is no longer in use. PR's are always welcome (and appreciated!) to improve the docs.
Yes, that would be technically possible. It doesn't really improve the product in any meaningful way, and adds a very small complication into the initial setup. It's not worth it. I don't expect us to bring back this functionality in the short term, without a particularly good reason for doing so. |
Beta Was this translation helpful? Give feedback.
As you've noted, that environment variable is no longer in use. PR's are always welcome (and appreciated!) to improve the docs.
Yes, that would be technically possible. It doesn't really improve the product in any meaningful way, and adds a very small complication into the initial setup. It's not worth it.
I don't expect us to bring back this functionality in the short term, without a particularly…