It will be removed in or after version 1.0įaraday::Error::ClientError.inherited called from /Library/Ruby/Gems/2.6.0/gems/octokit-4.14.0/lib/octokit/middleware/follow_redirects.rb:14. NOTE: Inheriting Faraday::Error::ClientError is deprecated use Faraday::ClientError instead. $ bundle exec jekyll serveĬonfiguration file: /Users/dylanbeattie/Projects//_config.yml So I grab a fresh clone of the PubConf source tree, do the bundle install / bundle exec jekyll serve invocation, and… boom. And apart from a couple of weird quirks that I’ve managed to isolate, it’s all good – including all my other Jekyll sites. It’s built using Jekyll and hosted on Github Pages, and I’ve had a local version of the PubConf website running on my Macbook for the last 4-5 months without any hassles… except last week, I repaved my Macbook with a clean install of macOS Catalina. Todd Gardner is taking a bit of a break from travel in 2020, so I’m going to be running PubConf London at the end of January – which means I get commit access to pubconf.io (yay!) for the next two months. And it starts, like so many things, at the pub.
I use Jekyll and Github Pages for pretty much all my standalone websites these days, and I love it – the combination of static HTML, Markdown and YAML provides just enough data-driven behaviour to avoid lots of unnecessary duplication, but without any of the costs or overheads of running databases and server-side processing. UPDATE: Thanks to the amazing power of Detective Twitter, I think we figured out what’s going on… Shaving the Jekyll Yak Posted by Dylan Beattie on
0 kommentar(er)
