Jekyll
Fingerprinting Jekyll SASS Assets
As I’ve been updating the stylesheets on my blog, I ran into an issue with browser caching — changes to my CSS weren’t showing up right away. Since I’m serving assets through AWS CloudFront with a 7-day cache for non-HTML files, this behavior makes sense. While I could disable caching altogether, that feels like a blunt and amateur solution. Instead, I’m implementing asset fingerprinting to keep the performance benefits of caching while ensuring everyone always get the latest version of my styles.
Tweeting New Jekyll Posts From Github Actions - Part 2
I previously wrote about my experience attempting to use Github Actions to post a tweet every time I publish a new post on my self-hosted Jekyll/S3/Cloudfront blog. I managed to get to a working solution that was too complicated, so I’m trying another approach. I was following this post by Dave Brock where he described using the commit message as the entire tweet - so every commit message and git push is a tweet. I dismissed it as too simple, but now that I’ve seen how complicated the alternative is I’m going to try something similar.
Tweeting New Jekyll Posts From Github Actions
This site is built with Jekyll and hosted on Amazon S3, with Cloudfront as the CDN. I recently did some work to make the deployments automated with Github Actions.
Hosting a Jekyll Site on Amazon S3 and Cloudfront
I recently reconfigured the deployment for my blog since I had switched to a new laptop. This site is built with Jekyll and hosted on Amazon S3, with Cloudfront as the CDN. The deployment of the site was done with the s3_website gem. I have both a staging and production environment, which is really useful to test any kind of changes - either to the blog config, styling, or anything with AWS configuration. I automated all of this with a simple bash script which could deploy to either environment.