Access files uploaded to Parse.com after Heroku migration -


i attempting migrate server parse.com on heroku 1 click migration. documentation says parse server supports "file" type, can't find documentation on transferring these files heroku can access them.

this isn't answer i've been having same issue/dilemma , have partial information might helpful in finding answer. did migration , took @ of stuff going on.

example, photoobj.get('file').url();

on parse hosting: files point following: http://files.parsetfss.com/parsefilekey/filename.ext

this stored on amazon s3 thing. points to: https://s3.amazonaws.com/files.parsetfss.com/parsefilekey/filename.ext

after migrating heroku/mongolab, photoobj.get('file').url() points following: http://files.parsetfss.com/newhostfilekey/filename.ext

newhostfilekey designate in parse-server setup , seems automatically generated via setting.

i don't see evidence far migration tool moves files parse hosting new host/db.


file uploading new host works fine. on new host, if 1 generates new file ends pointing this: http://newhosturl/parse/files/appid/filename.ext

parse whatever designate @ startup of parse-server app.use('/parse', api);

appid whatever designate @ startup of parse-server like

var api = new parseserver({ appid: 'appid', filekey: 'newhostfilekey' });

changing url point of parse hosted file fit new host pattern doesn't yield (file not found) etc.

i have no idea how new files being stored , url routes to.


with new files uploaded via new host, notice new tables/collections created in mongolab db. these fs.chunks , fs.files

fs.chunks data of file being stored (i think). under new heroku/mongolab setup, files seem reside "in" db.


as best way migrate images parse hosting new hosting is, have no idea i'm not sure there straightforward answer publicly out there @ point.


Comments

Popular posts from this blog

sublimetext3 - what keyboard shortcut is to comment/uncomment for this script tag in sublime -

java - No use of nillable="0" in SOAP Webservice -

ubuntu - Laravel 5.2 quickstart guide gives Not Found Error -