This post is about deploying a Highly Available Ghost CMS using DevOps practices on AWS - its both a deep-dive into the different AWS DevOps services, and a tutorial to follow to get a working, highly available Ghost blog running on AWS ECS deployed through a CI/CD pipeline.
Ghost [https://ghost.org/] is one of the most popular CMS and blog platforms,
rated 2nd on GitHub [https://github.com/topics/cms], and the biggest open
source
headless CMS project [https://headlesscms.
I've been running this Ghost blog since about 2017. I started off using the
default Casper theme, then used CoderGhostTheme
[https://github.com/mbejda/CoderGhostTheme] for while, before settling on Crisp
[https://github.
A few months ago I wrote about upgrading this blog's Ghost version from version
0.x to 1.x [http://hacksaw.co.za/blog/ghost-blog/]. Since version 2 has been out, here is
I recently changed came across the awesome worlds of fonts, because I got tired
of the default font in my email-client . I had been using Calibri for the last 5
years, and before
A few months, I mentioned how Nginx and Ghost was setup
[http://hacksaw.co.za/blog/2017/03/24/ngnix-and-docker/]
That was running version 0.9 of ghost. I finally decided to upgrade