From e84718eb5553ef3b6652902c1f526065d24334e1 Mon Sep 17 00:00:00 2001 From: domomills Date: Tue, 2 Jul 2019 13:12:18 -0700 Subject: [PATCH] Update README.me Added information about region codes for S3 buckets and removed bin/pip hint from dockerfile write hints --- workshop-1/README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/workshop-1/README.md b/workshop-1/README.md index fc52054..0363812 100644 --- a/workshop-1/README.md +++ b/workshop-1/README.md @@ -108,7 +108,7 @@ You will be deploying infrastructure on AWS which will have an associated cost. ### Checkpoint: -At this point, the Mythical Mysfits website should be available at the static site endpoint for the S3 bucket created by CloudFormation. You can visit the site at http://BUCKET_NAME.s3-website.REGION.amazonaws.com/. For your convenience, we've created a link in the CloudFormation outputs tab in the console. Alternatively, you can find the ***BUCKET_NAME*** in the CloudFormation outputs saved in the file `workshop-1/cfn-outputs.json`. Check that you can view the site, but there won't be much content visible yet until we launch the Mythical Mysfits monolith service: +At this point, the Mythical Mysfits website should be available at the static site endpoint for the S3 bucket created by CloudFormation. You can visit the site at http://BUCKET_NAME.s3-website.REGION.amazonaws.com/. For your convenience, we've created a link in the CloudFormation outputs tab in the console. Alternatively, you can find the ***BUCKET_NAME*** in the CloudFormation outputs saved in the file `workshop-1/cfn-outputs.json`. ***REGION*** should be the [code](https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region) for the region that you deployed your CloudFormation stack in, for example, us-west-2 for the Oregon region. Check that you can view the site, but there won't be much content visible yet until we launch the Mythical Mysfits monolith service: ![initial website](images/00-website.png) @@ -159,7 +159,6 @@ The Mythical Mysfits adoption agency infrastructure has always been running dire - Consider the [RUN](https://docs.docker.com/engine/reference/builder/#run) command - More on [pip and requirements files](https://pip.pypa.io/en/stable/user_guide/#requirements-files) - - We're using pip and python binaries from virtualenv, so use "bin/pip" for your command #[TODO]: Specify a listening port for the container