So today I killed ColdFusion Bloggers. This was rather abrupt and I apologize for that. A week or so ago it was reported to me that the data wasn’t updating. I logged into the service providing hosting and discovered they were shutting down for good in a few weeks. I’ve had free credit with them for a few years now, but honestly, I didn’t want to go find another cheap Node hosting solution.
I spent the last week at a company offsite in Panama (which is quite beautiful, although I spent most of my time in a hotel). During that time I participated in a hackathon using multiple IoT devices. One of them was this nice little LCD panel:
Before I begin, let me just state that what I’m covering today is already covered in the docs (Deploys - Netlify), but for me it wasn’t quite detailed enough and I wanted to run through, and then document, the process myself. I don’t know if this is helpful, and as always, I hope my readers will tell me, but I figured I’d share how it worked for me. Also note that VuePress is still early on in development, so what I describe today may not make sense in the far flung future of flying cars and jetpacks.
The last time I blogged on Jekyll, I was a bit upset with it. In fact, I said this: “So yes, I’m officially done with Jekyll.” But… things happen. At work, we use Jekyll for our docs and blog, and I actually had little to no difficulty getting both of those working in WSL on both my laptop and desktop. Given that experience, I began to think about migrating my blog back.
What spurred that even more was me finally figuring out how to get Jekyll to exclude most of my content locally. Maybe this wasn’t a feature last time I used it, but now it is rather trivial. Here’s the config setting I use:
With this in play, my startup and reload time is about four seconds. Still a bit slow but acceptable. (And if I really cared, I could knock out various months in 2018 as well.) While Hugo definitely has Jekyll beat on speed, I cannot describe how much I disliked using it. Everything it did annoyed me. To be clear, I’m not saying it is a bad project. It is incredible fast, has lots of features, and served me here well for years. But as a developer, I really disliked using it. On the other hand, I enjoy hacking around with Jekyll.
Using it with Netlify was pretty simple. I followed this blog post which basically came down to adding 2 files and changing my build settings. Build times are pretty decent too:
One thing I really like about this theme, but which may be a bit annoying to regular readers, is that every post has a clear callout to the author (me). At first that seemed a bit silly since every single post here is from me (I have had a few guest posts, but not in years), but since most folks come in here via a Google search and probably have no idea who I am, I think it will be a nice change.
Speaking of “regular readers”, note that I’m no going to use FeedBurner to host my RSS feed. If you want to subscribe to my RSS, just use this URL: https://www.raymondcamden.com/feed.xml. I’m toying with the idea of setting up an email subscription list, but I’m not sure if that is worth the effort.
The only real “bug” I am aware of now is that my tag and categories archive are single pages. That means I’ve got (nearly) 6000 links on them which is pretty ridiculous. Jekyll can’t generate new files so to fix this, I need to create files for each tag and category and have them run one simple template. That’s pretty trivial work, but I just haven’t done it yet. Once I do I’ll update the links on the right. There are a few Markdown issues on some older posts, but I’ll address those whenever I see activity (something I was doing on the old theme for even older posts).
Outside of that - well - I hope you like it!
Header photo by Artem Bali on Unsplash
A few weeks back a new static site generator was launched, VuePress. Being based on Vue.js, I was immediately interested in it. I’ve only been using it for a few hours, mainly prototyping it for something I’d like to build at work, but I thought I’d share a little code snippet I wrote. You should assume this is probably the wrong way to do it. As I said, I’m pretty new to VuePress, but when I get something working I like to share it.
First off - my apologies for being a bit quiet here. I had two trips in a row, some big things (good things) happening at work, and some projects that aren’t necessarily blog worthy yet, but hopefully I’ll have some cool stuff to share soon.
One of my goals for 2018 was to become an “expert on Vue”. While I think I’m years away from considering myself an expert, I’ve spent a lot of time digging into it and trying to become better skilled with it, and all the various things in the “Vue ecosphere” like Vuex, Veutify, and more. I’m happy to announce that this May, I’ll be giving a three hour course on learning Vue.js:
I’ve been playing, off and on, with Microsoft Azure for a while now. My main focus has been on the services areas (see my post comparing different visual recognition services) but I was also curious to see how well it worked as a PaaS for Node apps. About two or three months ago I tried to push a simple LoopBack app up and I was not successful. I put the blame on me for not reading the docs well, but it wasn’t a good experience. About a week or so ago I was talking to a Microsoft employee about deployment in general and when I mentioned my last experience, he pointed me to this great tutorial: