TL; DR Some time ago, I decided to multi-cloud my site. I’ve recently decided to revert to a single cloud hosting provider. I’m taking the opportunity to experience Amplify static hosting for this site.
Challenges with the previous configuration Multiple hosting locations meant multiple build processes.
In effect, the site was built, deployed (to Firebase) then rebuilt and redeployed (to AWS). Admittedly, the latter was rarely an overhead as the AWS Amplify CI/CD workflow was triggered upon commit to the master branch on CodeCommit.
Dual hosting a Hugo static site with two of the largest CDNs in the world.
4 minute read
TL; DR In this post, I’ll discuss a rabbit hole that I went down with only a thin excuse as the reason. And here it is, a Reddit reply to a shared post from this site:
I can’t view on my desktop because your site is blocked on my network. Sorry
The rabbit hole in question? Dual stacking this site across Google and Amazon infrastructure.
Introducing AWS Amplify I first read about Amplify in this blog post.