With the recent update to Google Chrome helping shape a more secure Web by marking all HTTP sites as “not secure”, I thought it was time that I make the necessary changes to how we host audio files for the Three Devs and a Maybe podcast.
In this post I would like to discuss setting up Caddy Server (which provides HTTPS out of the box!) as a static-hosting platform on AWS - provisioning the instance with Packer and the surrounding infrastructure using Terraform.
Up until now, we have spent our time setting up the API project to provide a confident testing pipeline (with types) and Amazon Cognito authentication.
We will now move on to implementing the first real API endpoint, that being the Bootstrap response.
Along the way we will configure Serverless Offline, allowing us to locally interact with the API, without having to provision any online resources.
In a recent Software Engineering Daily podcast Henry Zhu discussed the Babel project, and shed some light into how the transpiler works under-the-hood.
He touched upon how Plugins can be created to alter the resulting compiled code.
I was very interested in experimenting with this capability.
In this post I wish to highlight the process in which Babel transforms your code, developing several interesting plugins along the way.
Following on from adding Flow to the API project, I now wish to garner further confidence in the code by adding tests.
In this post I will document the process of setting up the test-runner Jest, and adding suitable test coverage to the current authentication example.
We have now settled on how our application will perform user authentication.
I now wish to take a step back and help improve upon our code confidence, by-way of adding the static type checker Flow.
In this article I will document the process of configuring Flow with Babel and Webpack, expanding upon our previous example by adding sufficient typing.