We’re still using ColdFusion 10 in production, but we’re using ColdFusion 11 for some new development (I doubt we’ll use ColdFusion 2016 until it’s been out in the wild for a few months.) One of the “new” features in 11 is
QueryExecute, which provides a more streamlined way to run queries from cfscript. I couldn’t find too much out there on how to use it, so I did a little digging as we started to implement it in our code.
We recently migrated to Mailgun (from SES on AWS) and in general have been thrilled with the change. The API is straightforward, testing is built in, and the data available is much, much better. It’s been a joy to use. We did, however, run into one issue when we made the switch.
This is the final installation in my three part attempt to get up and running with Jekyll and Github Pages. Part 1 recounted my wrangling with Ruby, Part 2 outlined the missteps I took while getting Jekyll to run, and this will be my overview of Github Pages.
Yesterday I wrote about getting started with Jekyll, which was really just recounting my difficulties getting Ruby set up and configured correctly. Once Ruby was configured and the Jekyll gem installed, I assumed that it would be a fairly straightforward process. It wasn’t. But it probably should have been.
This was supposed to be a post complaining about the standards, or lack thereof, applied by ThemeForest, to the Wordpress Themes they well. As I went to write it I noticed that TinyPress.co’s SSL certificate had expired, so it seemed as good a time as any to dive into Jekyll and handle this static blogging with Github Pages myself.
I want to blog, but never actually do. So I’m starting.