-
-
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
GridStoreAdapter files location #1131
Comments
@davimacedo would you set a publicServerURL, and use that as the base? Would that provide a proper fix for you? |
@flovilmart I will try today and revert to you. thanks. |
@flovilmart @davimacedo the publicServerURL didn't work here at back{4}app. We've tested through files being shown with "http://" (They're served under both HTTP and HTTPS protocols). But we needed it to be "https://" by default. That solved our problem, but we still think that there could be another way to do that, just like suggested on #1131 (comment). |
We are also behind nginx on AWS. Is it also possible to implement a custom GridStoreAdapter and configure it while creating the server? Something like this... var gridStoreAdapter = require('parse-server'). GridStoreAdapter; |
@seijiakiyama we're waiting on your contribution then! |
Because of https://github.com/ParsePlatform/parse-server/blob/master/src/Adapters/Files/GridStoreAdapter.js#L66 when using nginx (or other) to proxy requests, you don't have enough control over the files location url.
My suggestion is to use like it currently is as a default behavior but add an optional parameter in the GridStoreAdapter to set the file location (instead of the default config.mount).
I would like to know if a contribution about it would be welcome.
The text was updated successfully, but these errors were encountered: