-
-
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
Parse File Migration from Parse S3 #103
Comments
@viraj those files are still on Parse. The old PFFile objects you migrated will still point to the original files hosted on Parse. We are currently working on tooling allowing you to migrate those files. |
Thanks. Let us know when its ready. |
If you provide the File Key (from Parse dashboard), then parse-server can render the proper url key when ParseFile columns are included in query results. |
Continue discussion in #8. |
Any updates related to file migration now? |
@flovilmart Thanks |
If anyone else is looking for another Parse File to S3 migration tool, we made ours open source: https://github.com/modernistik/parse-file-migration If you are ok with Heroku, you can use the heroku deploy button provided and then delete the heroku instance once it has completed. |
note that the parse-files-utils is leveraging mongodb directly and the file adapters too, so not S3 specific. |
Hi Parse team,
I successfully migrated my app but I'm having difficult time accessing the PFFile.
Need your help.
The text was updated successfully, but these errors were encountered: