Skip to content

Stage Four

And now we reach the point where we start doing what the industry would call "DevOps". This means we'll now be taking all the code you've written - Terraform, Ansible, Packer, etc. - and we're now going to manage it via Continuous Integration and Continuous Delivery pipelines.

We're also going to do something special: we're going to write our own software to replace WordPress (it'll be really simple, don't worry) and then manage the lifecycle of that software using DevOps principles.

This all bridges everything you've learned into a big project that will see you gaining the skills you've been looking for: those of a DevOps Engineer.

Architect

This stage doesn't address any architectual changes or variations, hence there's no fancy diagram here. This stage is all about taking a step back and improving the code around Tightly.

Topics

  1. Testing our software
  2. Packaging our software
  3. Docker
  4. Security scanning (DevSecOps)
  5. Continuous Integration (CI)
  6. Continuous Delivery (CD)

Next

First things first, let's write some test suites for Tightly to ensure (or at least help ensure) we don't introduce regressions to it when we're adding features.