Skip to content

Commit 42eff13

Browse files
Update
1 parent 8180524 commit 42eff13

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ The individual services used will be:
1515

1616
All of this magic can be fairly tedious to work with from scratch, especially if you are not accustomed to AWS. Combined with the slow deployment times, it’s not really the most user-friendly mini-project I’ve done. I hope I spare some of you out there a bit of wasted effort!
1717

18-
The below helps with the overall steps for setting everything up, with some steps automated and some manual. Since my last version, Serverless Framework has added more support for Lambda@Edge functions, but still not enough to make my capable of deploying all the functions and setting up the Cloudfront the way it's needed. Note that I am not saying it's not possible, but you won't find it working like that in this repo. [You should be able to automate everything (minus function deployment) through Terraform](https://transcend.io/blog/lambda-edge-functions-in-terraform) if that's your poison of choice.
18+
The below helps with the overall steps for setting everything up, with some steps automated and some manual. Since my last version, Serverless Framework has added more support for Lambda@Edge functions, but still not enough to make me capable of deploying all the functions and setting up Cloudfront the way it's supposed to be. Note that I am not saying it's not possible, but you won't find it working like that in this repo. [You should be able to automate everything (minus function deployment) through Terraform](ttps://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudfront_distribution) if that's your poison of choice.
1919

2020
_An improvement on this prerenderer would be to include render-caching capabilities so you need to do less processing._
2121

@@ -24,9 +24,10 @@ _An improvement on this prerenderer would be to include render-caching capabilit
2424
### Prerequisites
2525

2626
- You will need an AWS account
27-
- Highly likely that you need to have the AWS SDK installed
27+
- You will need [Serverless Framework](https://www.serverless.com) installed if you are going to use the automated approach
28+
- Highly likely that you need to have the [AWS CLI](https://aws.amazon.com/cli/) installed
2829
- Highly likely that you need to be logged in through the terminal/environment
29-
- Optional: A REST client like Insomnia if you don't really love curl'ing in your terminal
30+
- Optional: A REST client like [Insomnia](https://insomnia.rest) if you don't really love to curl in your terminal
3031

3132
### Create a static build of a site
3233

@@ -147,7 +148,7 @@ Services that should be able to give you an indication of functionality:
147148
- Google Mobile-Friendly Test: [https://search.google.com/test/mobile-friendly](https://search.google.com/test/mobile-friendly)
148149
- LinkedIn: [https://www.linkedin.com](https://www.linkedin.com)
149150

150-
If you use Insomnia or Postman, you can try GETting your Cloudfront distribution with a header like `googlebot` and it should respond with rendered HTML. Removing the header should in turn start returning the basic HTML again.
151+
If you use Insomnia or Postman, you can try GETting your Cloudfront distribution with a `user-agent` header like `googlebot` and it should respond with rendered HTML. Removing the header should in turn start returning the basic non-rendered HTML again.
151152

152153
### Where to find logs?
153154

0 commit comments

Comments
 (0)