Skip to content
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

Closed
reknih opened this issue Sep 13, 2024 · 7 comments
Closed

[bitnami/discourse] Allow specifying GeoIP license keys in values #29391

reknih opened this issue Sep 13, 2024 · 7 comments
Assignees
Labels
discourse feature-request solved stale 15 days without activity triage Triage is needed

Comments

@reknih
Copy link

reknih commented Sep 13, 2024

Name and Version

bitnami/discourse 14.1.3

What is the problem this feature will solve?

When booting up, Discourse emits the following warning:

Please set DISCOURSE_MAXMIND_ACCOUNT_ID and DISCOURSE_MAXMIND_LICENSE_KEY. See https://meta.discourse.org/t/configure-maxmind-for-reverse-ip-lookups/173941 for more details.

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:

discourse:
  geoip:
    accountId: string # Goes into main config map
    licenseKey: string # Goes into main secret

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.

@github-actions github-actions bot added the triage Triage is needed label Sep 13, 2024
@javsalgar
Copy link
Contributor

javsalgar commented Sep 16, 2024

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?

Copy link

github-actions bot commented Oct 2, 2024

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.

@github-actions github-actions bot added the stale 15 days without activity label Oct 2, 2024
@reknih
Copy link
Author

reknih commented Oct 2, 2024

Commenting as the issue is not yet resolved

@javsalgar javsalgar removed the stale 15 days without activity label Oct 2, 2024
Copy link

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.

@github-actions github-actions bot added the stale 15 days without activity label Oct 18, 2024
@reknih
Copy link
Author

reknih commented Oct 18, 2024

Unstale

@github-actions github-actions bot removed the stale 15 days without activity label Oct 19, 2024
Copy link

github-actions bot commented Nov 3, 2024

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.

@github-actions github-actions bot added the stale 15 days without activity label Nov 3, 2024
Copy link

github-actions bot commented Nov 9, 2024

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.

@github-actions github-actions bot added the solved label Nov 9, 2024
@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discourse feature-request solved stale 15 days without activity triage Triage is needed
Projects
None yet
Development

No branches or pull requests

3 participants