You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe too late to ask but I have a self-hosted parse instance and all files are stored on grid currently. How can I move them to s3 now and start using s3 for new uploads? Can I leave earlier uploaded file on the grid and new files on s3 or do I have to move all old files as well to s3 if yes how can I move them to s3?
@a4arpan you can only have on file adapter on parse server at a time. As a result you will be accessing/saving to grid store or to S3 entirely, no in-betweens.
With this being said, I recently helped someone with a migration to a hosted solution from their own setup. To migrate the files across we ended up keeping the original parse server up to have access to those files. From there we utilized an SDK to request from the old parse server, and then save them to the new one; updating related parse objects along the way. Not the most elegant solution, but it worked in that case w/ 1000~ files or so. If you have significantly more that might be an issue for you.
A better solution would be to have them moved directly from grid store into the new file adapter storage mechanism. Maybe the above mention parse-file-utils does this, but it hasn't been updated in some time.
Activity
JeremyPlease commentedon Jul 19, 2016
You could use parse-files-utils to transfer the files. Parse Server doesn't currently allow multiple file adapters.
ckarmy commentedon Jul 19, 2016
THANKS!
a4arpan commentedon Dec 12, 2017
Hi
Maybe too late to ask but I have a self-hosted parse instance and all files are stored on grid currently. How can I move them to s3 now and start using s3 for new uploads? Can I leave earlier uploaded file on the grid and new files on s3 or do I have to move all old files as well to s3 if yes how can I move them to s3?
Thanks in advance
Arpan
montymxb commentedon Dec 14, 2017
@a4arpan you can only have on file adapter on parse server at a time. As a result you will be accessing/saving to grid store or to S3 entirely, no in-betweens.
With this being said, I recently helped someone with a migration to a hosted solution from their own setup. To migrate the files across we ended up keeping the original parse server up to have access to those files. From there we utilized an SDK to request from the old parse server, and then save them to the new one; updating related parse objects along the way. Not the most elegant solution, but it worked in that case w/ 1000~ files or so. If you have significantly more that might be an issue for you.
A better solution would be to have them moved directly from grid store into the new file adapter storage mechanism. Maybe the above mention parse-file-utils does this, but it hasn't been updated in some time.