S3 deployment is kinda broken

[kremalicious]

Upon deployment, gulp-awspublish puts all files into an unnamed folder, making site appear deleted. Happens for both, live & beta. Looks like that in S3 web console when going to root of bucket:

There is an issue for that but not clear if this is caused by the plugin or the underlying S3 library, or if that's only happening on eu-central-1 buckets: pgherveou/gulp-awspublish#80

For now, there's a manual workaround: after every Travis deployment we have to copy all files manually via S3 console from within the unnamed folder and paste them into the root folder. This means the site is down for about a minute, depending on how fast you can click around:

If this problem persists and is not fixed on the gulp plugin side, we have to write our own S3 deployment mechanism by using the aws s3 tool directly, like we do on oceanprotocol.com https://github.com/oceanprotocol/site/blob/master/deploy.sh