Gavin03 March 2018 03 Mar
I haven't set up a dev blog yet, so I'll use this for now. I just used letsencrypt.org to add HTTPS to squawk.online. It was *much* easier that I anticipated. EFF created a great little utility that does all the work, certbot.eff.org, it even updates your server config. The only stumbling block was that I forgot my firewall was blocking 443. The certs only last 90 days so next I'll have to set up a cron job to do that for me.
Someone bought Gavin 3 coffees.
02 March 2018
Thanks, Someone! For this I have done two things! I set up a prod instance so that the site breaks less often while I'm tinkering. More importantly, I set up HTTPS so that you can be sure your "pickle" squawk takes you to the right place.