HOWTO guide for front-end developers to enable Travis-based publishing to personal S3 bucket

[MikeTheCanuck]

Some Hack Oregon developers have never used TravisCI or AWS S3, and will probably require step-by-step instructions on how to implement the initial CI pipeline for their own S3 bucket.

Instructions should include:

• how to sign up for an AWS account
• creating an S3 bucket (using the AWS console)
• installing the TravisCI and AWS dependencies (if any)
• creating an AWS IAM account for use by TravisCI to publish files to S3 post-build
• setting appropriate permissions for the AWS IAM account in the S3 bucket to allow upload of files
• editing the .travis.yml file to include the developer's personal IAM creds, S3 bucket
• encrypting the secret_access_key in the .travis.yml file

Assume developers already know how to:

• install and use git client
• create and/or use github keys/credentials
• generate content that will successfully pass TravisCI smoke test
• clone and use the hack-frontend-starter project

Potentially could also cover (or reference):

• setting Everyone:read permissions on the bucket (for peer-based manual testing of solutions)
• creating an S3 bucket (using the AWS CLI)

Start with this content as a template: https://github.com/hackoregon/hacku-devops-2017/wiki/Assignment-2---Travis-CI-Introduction

[MikeTheCanuck]

Moot point. All frontend deployment will now focus on generating an npm package out of the frontend code and publishing it to npmjs.org.

S3 buckets will merely be used for static assets.

Further, the CI/CD knowledge in devops is strong enough that we will just setup the environments for each frontend team.