Synchronized a directory to a s3 bucket. It makes the bucket identical to the source-dir. Note that this means that remote files that are not in the source-dir are deleted. The synchronized files will get an public access level.

You can use application and deployment variables in wercker.

View this step in the wercker directory

Current status on wercker:

• key-id (required) The Amazon Access key that will be used for authorization.
• key-secret (required) The Amazon Access secret that will be used for authorization.
• bucket-url (required) The url of the bucket to sync to, like: s3://born2code.net
• source-dir (optional, default: ./) The directory to sync to the remote bucket.
• opts (optional, default: --acl-public) Arbitrary options provided to s3cmd. See s3cmd --help for more.

- s3sync:
    key-id: $KEY
    key-secret: $SECRET
    bucket-url: $BUCKET
    source-dir: $SOURCE
    opts: --acl-private

By default s3sync will make the files publicly available from your S3 bucket, but you can use the "opts" option to manually specify an ACL option to s3cmd. At the time of writing, these are:

  -P, --acl-public      Store objects with ACL allowing read for anyone.
  --acl-private         Store objects with default ACL allowing access for you
                        only.
  --acl-grant=PERMISSION:EMAIL or USER_CANONICAL_ID
                        Grant stated permission to a given amazon user.
                        Permission is one of: read, write, read_acp,
                        write_acp, full_control, all