Repository navigation
Status of legacy files on Parse S3 #8
Description
Activity
We'll be working on a plan for this. Right now when you migrate data, the files stay on Parse's S3 bucket, but parse-server knows how to continue serving them..
It would be so nice to have a config setting with our own S3 settings which end up getting used for file uploads.
So we are assured that file migration will be happening? So that we can continue develop using PFFile before migration?
@hashmapped Yes
Without PFFile migration my apps are dead in the water, please prioritise this as it would allow me to migrate alot sooner
So if I do a database migration right now, when a user creates a new PFFile - will the MongoDB entry just point to a new file hosted by Parse or will something else happen ?
New files uploaded to parse-server are hosted in GridStore(Mongo), only files uploaded through api.parse.com are still hosted by Parse. We are definitely going to solve this, and an awesome engineer here is working on an great update.
+1 we really need this. Do we at least have a timeframe for this? like when it likely will be available?
Also would be good if the client SDK can directly upload to S3 without hoping on first to parse server, abstracted in the client so we can still use the parse file api.
I would love to see a script that helps the user (idempotently) download every file from Parse's S3
http://files.parsetfss.com/endpoint and from GridFS, and uploads them to a third location of the user's choice (authentication might be an issue here of course — parse-server will need a way to handle this): whether this be an S3 bucket, or Dropbox, or Cloudinary, or whatever.The script should also update the URL held in the relevant Mongo file field for each class.
It's scary to think that after a year, all files held on Parse will disappear unless action is taken!
@fatuhoku that is very easy, I have already written one to copy all my files off Parse to an alternative server for backup purposes. Just use the javascript or php api's and you will get it done in minutes.
The real issue is that until I move to my own server files uploaded to api.parse.com are hosted by Parse.
What is needed is two fold.- When I tell api.parse.com that I want to move to MongoDB - to move all my existing files over as well as the database and store them with MongoDB Gridstore.
- When (1) above is complete and I have moved to my own MongoDB for api.parse.com to store all new files to MongoDB gridstore and STOP hosting the files yourself.
This way I can follow Parse's guide of step 1) point at own database , 2) build own server, 3) issue app update.
Currently with files this is not possible.
An alternative (or additional) process could be telling both api.parse.com and the new parse server to host files on a S3 instance instead of MongoDB gridstore.
Either way this is a glaring omission that needs resolving asap.@chrisfoulds do you have that script to hand by any chance? I'd be grateful if you stuck it on a gist so that we all have something to work off. Re. new files hitting
api.parse.combeing stored there, I imagine you could write a Cloud Code function (for every class that has files...!) that saves them to GridDB explicitly.64 remaining items
aaaaaannddd it's gone.
Hello everyone! We have just realized that lots of our files did not migrate completely to our servers and, as expected, we cannot access files on http://files.parsetfss.com/. This is core to our business and we need to get those files back even if we have to pay. Please, please, please, is there a way we can access them? We'll do anything that is necessary.
How come they can still access those files?
I have no idea
Hi, guys. We are doing like this:
parse-server-modules/parse-files-utils#67It is already merged to the master so you can still use parse-file-utils.
Parse.com announced it will stop anytime though.
Reacted by Seiji AkiyamaI migrated using sashido, just the files with mv.sashido.io.
Everything went fine and I can access the files in s3. but I can't access the files using parse dashboard, or my apps. what am I missing?@ortimanu ping me on [email protected]
- It might be permission issue sometimes.…On 31 January 2017 at 17:56, Manuel Ortiz ***@***.***> wrote: Hello everyone! We have just realized that lots of our files did not migrate completely to our servers and, as expected, we cannot access files on http://files.parsetfss.com/. This is core to our business and we need to get those files back even if we have to pay. Please, please, please, is there a way we can access them? We'll do anything that is necessary. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#8 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADRXACci3cXsU_RcEQ2s5NKKG5eZht_qks5rXyhvgaJpZM4HO2Bk> .-- alvajindia..... "nthng spzl..nthng mattrzz..."
- @mars If you are seeing access denied message, its because files were uploaded with limited permission. You can make the files public and then it will be available…On 1 February 2017 at 00:14, Mars ***@***.***> wrote: I migrated using sashido, just the files with mv.sashido.io. Everything went fine and I can access the files in s3. but I can't access the files using parse dashboard, or my apps. what am I missing? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#8 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADRXAI6dy2aNUzcFMLPh0lad4rwLu6ocks5rX4DygaJpZM4HO2Bk> .-- alvajindia..... "nthng spzl..nthng mattrzz..."
@alvajindia no, its giving me a "file not found" the urls have been updated with the mv-prefix do I need to set up a file adapter to make this work ?
- Did you set the Parse Public URL in your Parse-Server? I forgot to add it and all my file URLs started with localhost instead of the public URL. Can you check the URL that is giving your Parse-Server when accessing to files? El mié., 1 feb. 2017 7:45, Mars <[email protected]> escribió:…@alvajindia <https://github.com/alvajindia> no, its giving me a "file not found" the urls have been updated with the mv-prefix do I need to set up a file adapter to make this work ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#8 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAsPn5473tJ-lTrjhB1xLY0-wEt_Vgd2ks5rYCoXgaJpZM4HO2Bk> .
@arturogutierrez the file urls are pointing to the right domain as far as I can see in the parse-dashboard
a migrated file looks like this
https://[mydomain]/apps/[myapp]/files/[filekey]/mv-b0acb1ae-d6f7-44c9-921d-0f332366692a-file
newly uploaded and working files look like this, these were uploaded to my local parse
https://[mydomain]/apps/[myapp]/files/[filekey]/7213555b291d0c4ca7f99942c460a9ee_fileCould the file adapter cause this?
Guys, thanks to parse-server-modules/parse-files-utils#67 I could download all my files and transfer them to my S3 bucket. Thanks guys for everything!
What will happen to file migration? I can't really find instructions on how to transfer/migrate over files to your own bucket.