Replacing an old release

I've been caught in jobs dealing with the pain of being on old releases and needing to do an upgrade- the uncertainty of an unknown upgrade path, reading through volumes of change logs, the discussions about the unknown unknowns, and the extra push to do upgrades better.  Given all of this, I am good about prioritizing upgrades at work... but apparently not for myself!  

I was on such an old version of Ghost used on this blog, I needed to start from scratch for upgrading.  My ghost-on-aws repository now has instructions that should work for others when using the latest Ghost.  I didn't include everything I did, like the new-to-old migration paths I did with EBS volumes, but it does include other new good things to do, such as HTTPS. And with "ghost upgrade", I'll now be able to be good to myself and stay on the path of incremental upgrades.