– The podcast is not sponsored and it’s done in Nick’s spare time after hours

– What’s involved end to end to put together an episode

– Each episode gets about 400 downloads or listens but it’s hard to track

– Motivation for using Jekyll and Ruby

– A couple of custom Jekyll plugins to help building a podcast site

– So many static generators to choose from, just pick one

– Use the tools that you like and don’t constantly second guess yourself

– What is Liquid (Jekyll’s templating language)?

– The custom audio player is the only real amount of JavaScript on the site

– Jekyll-Assets is being used to MD5 tag static file names for cache busting

– nginx is serving the site with Let’s Encrypt handling the SSL certificates

– The only SAAS tool being used is Google Analytics but I don’t use it for much

– A few static sites are all hosted on a $5 / month DigitalOcean server

– The server load is at 2-3% CPU with 60,000+ monthly visitors

– Debian Bullseye is running on the server

– Ansible is used to provision the server

– Deploying a new podcast episode to the site

– Making sure all tags are properly filled out

– Another shell script to auto-inject an episode’s length and file size in bytes

– There’s no secret management because there’s no secrets

– The code is backed up on GitHub and an external USB HDD

– DigitalOcean’s built in monitoring and alerting as well as Uptime Robot is being used

– Best tips? Find tools that you’re genuinely happy using and stick with them

– You can find Nick on his site, @nickjanetakis on Twitter and nickjj on GitHub