You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ The individual services used will be:
15
15
16
16
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!
17
17
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.
19
19
20
20
_An improvement on this prerenderer would be to include render-caching capabilities so you need to do less processing._
21
21
@@ -24,9 +24,10 @@ _An improvement on this prerenderer would be to include render-caching capabilit
24
24
### Prerequisites
25
25
26
26
- 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
28
29
- 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
30
31
31
32
### Create a static build of a site
32
33
@@ -147,7 +148,7 @@ Services that should be able to give you an indication of functionality:
147
148
- Google Mobile-Friendly Test: [https://search.google.com/test/mobile-friendly](https://search.google.com/test/mobile-friendly)
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.
0 commit comments