From 2fedce8411f581eddf5ed3a4672186ca20a78ce2 Mon Sep 17 00:00:00 2001 From: Katie McLaughlin Date: Fri, 6 Feb 2015 13:45:10 +1100 Subject: [PATCH] Format `awsconfig` sample config correctly Reflow change in commit 195f3a3f removed newlines in the config format. This change reverts the sample config to the original formatting, which matches the actual config format of a `awsconfig` file. Signed-off-by: Katie McLaughlin --- docs/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/README.md b/docs/README.md index 4121fe7235..3b471555cd 100755 --- a/docs/README.md +++ b/docs/README.md @@ -89,8 +89,10 @@ you need to access the AWS bucket you'll be deploying to. The release script will create an s3 if needed, and will then push the files to it. - [profile dowideit-docs] aws_access_key_id = IHOIUAHSIDH234rwf.... - aws_secret_access_key = OIUYSADJHLKUHQWIUHE...... region = ap-southeast-2 + [profile dowideit-docs] + aws_access_key_id = IHOIUAHSIDH234rwf.... + aws_secret_access_key = OIUYSADJHLKUHQWIUHE...... + region = ap-southeast-2 The `profile` name must be the same as the name of the bucket you are deploying to - which you call from the `docker` directory: