replace domain name with direct S3 access

[bnham]

files.parsetfss.com, files.parse.com, etc. are now down. You can still access files on those hosts if you use the S3 bucket names (for now--these buckets will be taken down soon).

this is an untested diff which replaces https://files.parsetfss.com with https://s3.amazonaws.com/files.parsetfss.com, etc.

[codecov-io]

Codecov Report

Merging #67 into master will increase coverage by 0.08%.

@@            Coverage Diff             @@
##           master      #67      +/-   ##
==========================================
+ Coverage   15.58%   15.67%   +0.08%     
==========================================
  Files           4        4              
  Lines         263      268       +5     
  Branches       77       77              
==========================================
+ Hits           41       42       +1     
- Misses        222      226       +4

Impacted Files	Coverage Δ
lib/transfer.js	19.83% <16.66%> (ø)	✅

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 43726a4...717a59c. Read the comment docs.

[obibring]

@bnham, ran this, it worked. Thanks!

[maryamzafar]

Because of a serious client misunderstanding we were not able to migrate them before.. this worked like magic, I was able to download the files on my local system.

[bnham]

Parse shut down on Mon 1/30. The domains used by files (e.g. files.parsetfss.com) are now down, but for the moment you can still access those files by accessing the Amazon S3 bucket instead ( https://s3.amazonaws.com/files.parsetfss.com/...). That's what this PR was about, so you should try to download your files now using this utility. Note that direct access to files via S3 buckets will also be shut down sometime this week so you should use this tool to get your files sooner rather than later. If you have further questions, you should direct them to migration@parse.com .

…

On Wed, Feb 1, 2017 at 3:47 AM, maryamzafar ***@***.***> wrote: How do I migrate my files now? :-( Because of a serious client misunderstanding we were not able to migrate them before.. any luck now? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#67 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADXYmPm589ap9N4m5o3xwxQT6oRegMPqks5rYHDGgaJpZM4LyFOz> .

[gowridev]

I unable to access the files using the above approach. Could please provide an example how access the file.(https://s3.amazonaws.com/files.parsetfss.com/...).

I am getting below error ,when i give "https://s3.amazonaws.com/files.parsetfss.com" as parse server url
"\nAccessDeniedAccess DeniedF7D6C9AD2A83B238TEFcExG0r6O71ENrGthcbyyqkcehgN3nq8Yu04/Gw51von+H4xOxoPYGIb5hlV8tiBeURm3gQSE="

I am getting the below ,if i give server URL equal to hosted parse server instead of serverURL: "https://api.parse.com/1".
Failed request (404) skipping: https://[serverURL]/parse/files/ILTUQMCBqUe0tIY1fD6YSGnp7bxvkqEKYmTZ6I5q/tfss-fd9cefa9-4d91-4a82-b37f-734e83cca8b1-image.png

Is there any chance to access the files.

[bnham]

So there are two types of data we're talking about here:

• Database data (which is where your ParseObjects are stored). You used to access this db data through https://api.parse.com/1. Since api.parse.com and all the databases backing it were shut down on Monday, you can no longer access this data via api.parse.com. You can only access this database data if you've migrated your Parse data to your own self-hosted Parse Server instance. So to answer your question, the serverURL you should provide to the script is the URL of your self-hosted Parse Server instance.
• File data, which is where large binary objects (ParseFile) such as images were stored when you used Parse. This data was stored on Amazon S3. There used to be two ways to access this data: first indirectly via our domain name https://files.parsetfss.com/..., and secondly via a direct Amazon S3 URL that looks like https://s3.amazonaws.com/files.parsetfss.com/.... The first option (access via https://files.parsetfss.com/...) no longer works as of Monday. As of this writing, the second option (access via https://s3.amazonaws.com/files.parsetfss.com/...) does work, but it will probably stop working soon. All this pull request does is replace all instances of https://files.parsetfss.com/ with https://s3.amazonaws.com/files.parsetfss.com/. This replacement is automatic as long as you are running an up to date version of the script.

For further support you'll probably have better luck by starting a thread with migration@parse.com.

[mkpazon]

Is this still working?

[hramos]

Files are no longer available on Parse, now that the service has entirely shut down. The parse-files-util script can no longer be used to migrate files from the hosted Parse.com service.

[flovilmart]

@hramos we should probably close the repo or put something there.