Brian Ó Donnell

Is this project abandoned?

AFAIK it should still work, it just accesses the bucket by an alternate method. Someone with an s3 account should probably verify though.

I appears that AssetSync isn't so easy to override the defaults on, so while this patch makes uploads work, assets still try to go to s3.

Just uploads, I think. Doesn't D* get the url path from configuration > assets > host?

Yes, I believe it does change the urls from 'bucket.example.com' to 'example.com/bucket', but AFAIK Amazon supports both styles. Would you like me to add comments and resubmit, or do you...

Ok. What's the best way to deal with that? Throw an exception?

I have worked a bunch with Django and I've also done some websockets stuff with Tornado (though I understand Django 1.10 has some in-built WS support now). I'd be happy...

@matiasdelellis I can confirm that this problem still exists in 25.0.1 Can you give me some clues about what was supposed to be fixed so I know what to look...

Same result :(

Thanks. I appreciate it.