Ray Nicholus

Has anyone had a chance to test this out with Google Cloud Storage's S3 compatibility mode yet?

You'll need to ensure all access keys server side are your cloud storage keys. Also, the [`credentials.accessKey` client-side Fine Uploader S3 option](http://docs.fineuploader.com/branch/master/api/options-s3.html#credentials.accessKey) must be set to your GCS access key.

It looks like you are essentially uploading the file twice (once to your server, then again from your server to the final storage destination), something that Fine Uploader S3 aims...

Hmm, ok. I'll admit I'm not very familiar with app engine. Not very = not at all. Thanks for posting this, perhaps it will be useful for others using AE....

Shelving this until sometime after 5.3, unless someone reports success using Fine Uploader S3 w/ CDN support in the meantime.

:thumbsup: My limited experience with jekyll has been positive.

Sems docfu is working well enough for us. Any plans to overhaul it, @feltnerm?

All properties of the `credentials` option, other than `accessKey` are only intended to be used by client-side signing workflow. If you'd like to sign requests on your server, do not...

You can read more about the client-side upload/signing process [on the associated feature page in the documentation](http://docs.fineuploader.com/branch/master/features/no-server-uploads.html). If you do not want to handle signing client-side with short-lived credentials, use...

It's not clear _why_ you would like to provide temporary credentials when your credentials are stored safely on your server and never exposed to the client. If you'd like to...