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.
When ever we talk about APIs, people always think about the legacy ESB/SOA/ESF
stack. They are not meant to solve the same problems.
* SOA uses APIs – that’s about the only
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
There are a few popular and well known cases where companies have reinvented
themselves
[https://money.howstuffworks.com/10-companies-reinvented-themselves.htm], to
adapt to the times and market, and stay more relevant (I've written
"The race to serverless"
I've written about Operations here
[http://hacksaw.co.za/blog/2017/12/07/alerting-monitoring-and-dashboards/] and there
[http://hacksaw.co.za/blog/2017/12/17/operation/], and my thoughts on
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