Open balupton opened 6 years ago
Got this too.
I also got the same error.
Same here !
I'm also seeing this same issue in 1.3.2. Downgrading to 1.3.1 solved the issue.
Yeah. download this stout 1.3.1 version.
Downgrading to 1.3.1 doesn't fix the issue for users of the eu-central-1 region (and possibly other regions), because they only support the newer Amazon V4 signatures. Stout uses the older V2 signatures (and should probably migrate away from them), @zackbloom
I'm getting the issue with 1.3.1 now as well.
Seems there are a bunch of alternatives: https://github.com/search?o=desc&q=static+deploy+s3&s=stars&type=Repositories
Will try one of them.
Ended up moving to now.sh. The process is pretty simple.
npm uninstall cloudflare-stout
npm install --save-dev now
now teams switch yournowteam
optionalnow domain add --external yourdomain
now
to deploynow alias
to make the last deployment live
going back to stout 1.3.1 fixed this: