Doc enhancement - cache location

[arubdesu]

Just to get it logged, the readme may benefit from containing the fact that images are cached in the users ~/Library/Caches/com.google.corp.Restor directory(and obvs filenames/sha256's should match). Thanks!

[arubdesu]

Two points of clarification as of 1.7: one, don't put the file into place before launching the app (it's a 'cache', duh) and two, name it the same as you're displaying in the drop-down in the conf

[russellhancox]

One of Restor's 'features' is that the cache is automatically managed - old images are erased if they no longer appear in your configuration, new images are downloaded as needed, hashes are verified when the config is checked, etc. I don't really have a problem with documenting where the cache is but I'd like to understand what people are doing with the cache manually?

[arubdesu]

It's actually because of behavior I think is a bug but I haven't confirmed isn't a cloudfront issue - I have a policy on my (cloudfronted) S3 bucket to limit where the images can be accessed from (naively, I know.) Cloudfront URLs that work in Safari have not been working in Restor, and therefore we're using the S3 URLs in the config - which is super slow for an ~8GB download in regions that aren't close to the bucket. Being able to sideload the images to the cache (versus using the custom image pref) means we can still use the dropdown in the interface once the filesystem artifact is populated.