-
-
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 migration to heroku/aws regarding the images #420
Comments
+1 Still a missing piece of info in the tutorial. |
so what is the alternative ? |
There's a pull request open #113 that adds supports for saving files on S3 as well as a migration tool for existing files and also a files adapter, at the moment it's still safe to keep files hosted on parse |
@christianmarth thanks for reply |
When I tried the migration tool to (transferring to MongoLab), I ran into an issue with files. Here is my issue: When I export the data to JSON using Parse's export tool from the data browser on Parse, I see sufficient data about that photoFile field (example below):
Now, when I look in the new MongoLab collection for that _User collection, it just has the filename listed instead. No type or location data (URL) is provided as with the JSON export above:
Questions:
|
You need to include your fileKey when initialising parse server.
When you do a request that includes a file the full URL will be returned to you. You should be able to access files the same way on your client as previously so no change is needed on the client side. For migration to S3 you'll need to wait until the files adapter is complete and the documents are updated regarding the migration. |
@christianmarth will parse allow the file migration to s3 if I have already finalized the db migration to parse. since file migration is not available but I am doing the db migration now, or do I need to wait for the files adapter to complete to finialize the migration. |
Yes wait for the file adapter to be completed then a migration tool will become available #8 Any new files uploaded using parse server will be hosted on parse.com and will still be accessible until the service is closed down in 2017 |
Thanks for your help
|
Is there documentation on using your own s3 bucket? |
I am also facing the same issue. I have migrated the database. Created s3 bucket. My migrated app is working fine now, but the image files are till on the Parse s3 bucket. What will I do now? I have followed the above steps but got no success.... No documentation found. Please Help!!! |
I have successfully migrated my parse db to aws but the urls of image files still like 'http://files.parsetfss.com/77447afb-f681-4b55-afad-6bceeb2e155a/tfss-79297c86-bd48-4d7f-87ab-c43e02d1a8f3-photo.png'
it means files are still on parse s3 cloud or something their own storage so what will happen to those files after parse shutdown.
what is the way to migrate the images to new database/storage on my own AWS. I am worried because I have apprx 14.5 k images on parse.
Please provide you valuable guidance on this.
The text was updated successfully, but these errors were encountered: