This tutorial explains how to deploy automatically from bitbucket (or github) to AWS S3.
- Go to Create Application
- Select use bitbucket (or github)
- Choose your repo
- For the next questions, choose the default answers
box: wercker/default
deploy:
steps:
- s3sync:
key-id: $S3_ACCESS_KEY_ID
key-secret: $S3_SECRET_KEY
bucket-url: $S3_BUCKET_NAME
- on AWS, go to
Security Credentials
- Go to
Access Keys (Access Key ID and Secret Access Key)
- Create a new key and keep the
Access key ID
and theSecret Access Key
in a safe place.
- on Wercker, go to the settings of your app
- in
Deploy targets
, click onadd deploy target
and choosecustom deploy
- Target name can be
production
- Select Autodeploy
- Branch name is
master
- Click on
add new variable
and create a new environement variable with the nameS3_ACCESS_KEY_ID
and your access key id as text - Create another new variable with the name
S3_SECRET_KEY
and your secret access key as text - Create another variable with the name
S3_BUCKET_NAME
ands3://example.com
as text (change example.com with the name of your bucket)
Wercker should run the build (that does nothing so far) and deploy on s3.
I'm having the same issue that @ericpeters0n was having. I followed these steps exactly and I get the following error after a git push:
setup environment No pipeline named wercker.yml
Yet right after that it shows exactly what is in my wercker.yml file that is commited to the root of the repo.