-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
docs: databaseOptions
missing in Parse Server Options docs
#8168
Comments
Ha! I must have looked at an old API version. Are there other DB options missing? If any custom options are just passed to the adapter, we don't need to document them. But if supported options are explicitly defined, we should document them all. |
I'm pretty sure databaseOptions can be any valid options that can be passed to Mongo, Postgres, or any other valid database adapter |
Do we have any other custom options, like |
I think |
So this issue can actually be closed then? Maybe we should add to the docs somewhere that any other parameter is passed directly to the DB client? In any case, this issue belongs to the parse-server repo, because the API docs are generated from the definition files, right? |
I think it can stay open but transferred, it would help to explain to users that any other database options get passed directly to the db client |
OK, I'll transfer this to Parse Server and maybe you can do a PR to somehow add that note to the API docs, then we can close this. |
Thanks for opening this issue!
|
🎉 This change has been released in version 5.3.0-alpha.27 |
🎉 This change has been released in version 5.4.0-beta.1 |
🎉 This change has been released in version 5.4.0-alpha.1 |
🎉 This change has been released in version 5.4.0 |
🎉 This change has been released in version 5.4.0 |
The
databaseOptions
are not documented in the Parse Server docs. Instead it's just anAny
type.The correcting approach is to add a new Type and specify all the
databaseOptions
in that new type. See for example thePages
option.This is a crucial part of the documentation for everyone who is using multiple Parse Server instances, e.g. behind a load balancer. The
databaseOptions.enableSchemaHooks
option is an essential configuration, see #7214.The text was updated successfully, but these errors were encountered: