One branch to rule them all | guided series #1

Hey, author of the too long; automated blog here!

I had a problem in one of my projects recently: how to deploy my application to multiple cloud environments? The list of requirements was rather short:

--- Git flow must be a no-brainer–we don’t want to deal with multiple branches that will have to be frequently synchronized with one another.

--- Application needs to be versioned.

--- It must be possible to deploy a required version of the application to the selected deployment environment.

--- Every environment runs only one version of the application at the same time.

As I’m a data engineer and enjoy automating repetitive stuff, I added an extra one:

--- Automate manual processes to a reasonable extent.

I think (and hope) that both the end result, and the path that took me there, will be an interesting educational experience for you.

This post is the first one in a short, guided series. It’s titled “One branch to rule them all”, because, as you’ll find out, I’m going to use one long-lived branch to configure all of the deployment environments I need.

If you have any thoughts/feedback on it, I’d be humbled to hear it. Here, or directly on Substack.

Thanks a lot, and stay tuned for the upcoming posts if you enjoyed reading this one!