I still have a lot of old projects using yarn 1.x and I need to record the instructions somewhere
Putting my money where my mouth is, I configured a Content Security Policy (CSP) for my blog (amongst others) and in doing so I had to do some minor refactoring.
Using GitHub Actions to prevent the repository from breaking the developer experience due to automated package updates.
An unusual situation we encountered with one of AWS Lambdas not picking up new configuration despite the fact we had deployed it multiple times; and the fix.
As part of protecting your site and your users you should really consider applying a Content Security Policy (CSP) to your site. Here I detail on how I go about setting one up and the possible tools available to ease your pain.
Docker (and not just Docker Desktop) on a MacOS can be awfully slow, especially for developers when the container is accessing files on the local drive via a volume mount....
Creating an AWS Lambda and triggering on time
If you've read any of my earlier posts you'll know that I have been running the administrative side of my blog (using Ghost) on Heroku. But in this age, things move quickly and Ghost has since updated to v4 but looking at their docs the supported upgrade path is all around the ghost-cli tooling...
When I moved to using a Mac for development and working on projects involving React.js etc I knew I was going to have to reintroduce myself to the command line and so I started a search around what is the best terminal emulator and shell to use. During this search, I stumbled across oh-my-zsh...
Committing secrets to source control is a real problem for developers and I like many others have done it at least once.
Finally I completed the task of hosting the Ghost CMS on Heroku (free) [that I ashamedly admit I started this task in January and then deferred], then using Netlify I build and host a Gatsby.js generated static site.
Investigations into using Gatsby to build a static site version of my Ghost CMS blog using the services of Netlify and Render.