-
Notifications
You must be signed in to change notification settings - Fork 23
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
mongodb+srv urls with querystring parameters cause the forum to fail #16
Labels
bug
Something isn't working
Comments
@ghassanmas can you please describe how you launched a Mongodb cluster and how you defined the mongodb host url that caused the error you observed? |
1- Generating a cluster through atlass MONGODB_AUTH_MECHANISM: SCRAM-SHA-1
MONGODB_HOST: mongodb+srv://username:password@x-host.mongodb.net/?retryWrites=true&w=majority
MONGODB_USE_SSL: true
RUN_MONGODB: false
|
regisb
added a commit
that referenced
this issue
Mar 20, 2023
When the MONGODB_HOST url contained querystring parameters, the forum was failing because the outdated mongodb gem does not support them. So we just trim them from the setting. Close #16.
regisb
added a commit
that referenced
this issue
Mar 21, 2023
When the MONGODB_HOST url contained querystring parameters, the forum was failing because the outdated mongodb gem does not support them. So we just trim them from the setting. Close #16.
regisb
added a commit
that referenced
this issue
Mar 22, 2023
When the MONGODB_HOST url contained querystring parameters, the forum was failing because the outdated mongodb gem does not support them. So we just trim them from the setting. Close #16.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mongodb+srv urls are introduced in this PR: #10
But querystring parameters will not work in the forum because of the way the
MONGOHQ_URL
variable is generated:We need to modify the definition of
MONGOHQ_URL
such that querystring parameters are supported. If possible, we should take this opportunity to get rid of the forum entrypoint entirely.The text was updated successfully, but these errors were encountered: