-
Notifications
You must be signed in to change notification settings - Fork 11.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
MONGO_OPTIONS stopped working #12802
Comments
I will test if this solves the issue. Though I would challenge if the cors.js file is the correct place to set such a crucial database connection option. For me it seems that it worked kinda unintentionally all the time, given the file the function call is placed in. This should be one of the first things when initialising meteor. |
sorry guys, the error still exists on 0.74.1 |
@MarcosSpessatto @rodrigok ideas? |
@micfung can you please provide the content of your env variable |
@MarcosSpessatto My
i will take a look the link you give me. FYR. i can connect mongo from my rocketchat server using cli |
the command i use to connect mongo from my rocketchat server
|
With 0.72.0 it seems that MONGO_OPTIONS stopped working.
The file that loads this environment variable was last touched here: #12595
The environment variable is normally loaded here:
https://github.com/RocketChat/Rocket.Chat/blob/develop/packages/rocketchat-cors/server/cors.js#L18
Suspicion is change to module has effected the order this code is executed in. This needs to be executed very early in start up.
This seems very likely would effect other functionality in this file
The text was updated successfully, but these errors were encountered: