-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
ParseFile #29
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
Comments
Im also interested in how ParseFile (current Files) will be handled. I haven't yet wrapped my head around a clear migration path for this... |
I understood that the files are saved directly to mongodb |
@wagnercsfilho I thought they were pushed up to s3. |
#8 This seems to suggest using Parse Server will point to old files (Which are on s3, not saved on the db), and I suppose future uploads should use ones own storage/s3 account. |
But parse the code server are pointing to mongo using Mongo ( GridStore ) in GridStoreAdapter. GridStoreAdapter |
New file uploads are using GridStore by default, and if you migrated data from Parse the old files stay on the Parse S3 bucket. We'll figure out the best approach for moving old files, if there is a way. |
How difficult would it be to build an adapter for S3 so that developers can use their own buckets? |
What would be the strategy for storing files as Parse will not be hosting files anymore? Would this be a blessing in disguise? Can we now be able to host files larger than the 10mb limit in ParseFile if we implemented ParseFile ourselves?
The text was updated successfully, but these errors were encountered: