-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[bitnami/discourse] Allow specifying GeoIP license keys in values #29391
Comments
Hi! Thank you so much for the feature request. I will forward it to the team but as it is not a critical feature, we cannot guarantee an ETA. However, if you want to speed up the process, you can submit a PR and the team will review it. You said that you configured the extraEnvVars value, this is strange as it should work. Did you enter the container and check that the env vars are indeed set? |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Commenting as the issue is not yet resolved |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Unstale |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/discourse 14.1.3
What is the problem this feature will solve?
When booting up, Discourse emits the following warning:
Without current GeoIP databases, some moderation features of the Discourse forum are degraded.
What is the feature you are proposing to solve the problem?
Add a value to the chart that allows setting this. This could look as follows:
What alternatives have you considered?
I have tried using
discourse.extraEnvVarsSecret
to supply these values myself. This had no effect, likely because the underlying Docker image (bitnami/discourse:3.3.1-debian-12-r3
) does not propagate these environment variables to the application.The text was updated successfully, but these errors were encountered: