Browse code
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 <katie@glasnt.com>
Katie McLaughlin authored on 2015/02/06 11:45:10Showing 1 changed files
| ... | ... |
@@ -89,8 +89,10 @@ you need to access the AWS bucket you'll be deploying to. |
| 89 | 89 |
|
| 90 | 90 |
The release script will create an s3 if needed, and will then push the files to it. |
| 91 | 91 |
|
| 92 |
- [profile dowideit-docs] aws_access_key_id = IHOIUAHSIDH234rwf.... |
|
| 93 |
- aws_secret_access_key = OIUYSADJHLKUHQWIUHE...... region = ap-southeast-2 |
|
| 92 |
+ [profile dowideit-docs] |
|
| 93 |
+ aws_access_key_id = IHOIUAHSIDH234rwf.... |
|
| 94 |
+ aws_secret_access_key = OIUYSADJHLKUHQWIUHE...... |
|
| 95 |
+ region = ap-southeast-2 |
|
| 94 | 96 |
|
| 95 | 97 |
The `profile` name must be the same as the name of the bucket you are deploying |
| 96 | 98 |
to - which you call from the `docker` directory: |