The Second Update
So, I logged into the Ghost admin panel and saw an update notification staring back at me. Remember my first update?
I didn’t read the changelog. I simply decided to update. This time it was simple. All I did was backup my Ghost directory, wget the latest release, unzipped it (overwriting everything) and restarting the Ghost service. It works fine.
Still not as simple as WordPress, but painless for sure. I think theme updates are more painful.
The First Theme Update
A few days ago, an update for the theme came out. Normally, I wouldn’t care (I mean if I was on WordPress or something, I definitely wouldn’t). But to fully experience the transition to Ghost for blogging, I decided that it would be unfair for me to ignore this opportunity. So, I downloaded the theme zip from GitHub, made the necessary modifications for comments and the Tweet button, uploaded and applied the theme using the admin interface of Ghost.
The first thing after the page refresh was the not-so-subtle red colour in the heading font. On reading the changelog, I found that the author of this theme had included themes support for post headings, etc.
The Second thing I noticed was a red border on the top of the page. I’m sure people like borders on top, but I don’t. Again, the border colour could be changed using the theme selection in one of the hbs files (it was default.hbs, in case you want to know).
The third thing was the fonts. They were much larger. It made me feel that the subtlety of the theme that made me choose it when I put it to use on this blog was completely lost.
After sometime, I decided to revert to the theme I originally chose (version 0.1.4) and decided to not update the theme until something really breaks. I liked the smaller fonts. I liked the borderless design. I didn’t care for the improvements made to it. I’m sticking with version 0.1.4.
This also made me examine the theme code for Ghost themes and I realised that theme updates are not useful for anyone who is happy with the theme he/ she is using.
The First Update (to Ghost 0.11.1)
So, as a part of managing a blog, installing software updates and patches are important to keep your blog secure and relatively bug free.
I was greeted today in my Admin page that a new update to Ghost was out. This was Ghost 0.11.1. Frankly, I don’t even remember what version I was on.
Normally, I wouldn’t care for the update until it really brought some serious, crazy super-cow powers. But then this is not supposed to be normal. As a part of this experiment, I need to do this. So I headed to the "How to Upgrade Ghost" page and stared at it for 5 minutes before realising how much simpler this is on WordPress. I mean you just click "Update" and it takes a few minutes or seconds and you’re done (of course the ugly part of the process comes when plugins and themes start to misbehave at times but that happens only after a very major upgrade). But, dedicated to the experiment (for myself more than others, wait, others who?!), I decided to do it.
So, the process was not straightforward as a 1-click. It involved taking the blog offline, removing the engine files, making a copy of my content, extracting new files on to the web-server path, resolving dependencies and installing (this was just one command so that was good), realising that I need to also clear the cache, clearing the cache and finally seeing it work.
You’re now looking at a blog with the latest Ghost installed (as on this date it is 0.11.1). It won’t make much of difference to you (or to me for that matter) but it should be slightly improved, I guess. You can see the changelog here.
So yeah, that’s done.