I've been using GCP lately for a toy project. Today I got a warning from GCP that my tiny bills had increased four-fold. What happened? It turns out that even a toy instance of PostgreSQL is rather pricey compared to other cloud providers.

As part of exploration of Google Cloud services, I set up an automated build and deploy process for this website. In this post, I look under the hood and see how the simple getting started wizard I used, wires everything together. Over the past 14 years Google Cloud has build up over 100 services on offer. Unfortunately, there does seem to be a lot of duplication that confuses things.

A quick tutorial on an easy way to configure an automated build and deploy pipeline with GitHub and Google Cloud Run. Bonus: hosting is free for small projects.

As part of spinning up this blog, I decided to check out google cloud and get a basic feel for how it works. The TLDR is that even after 14 years on the market it feels relatively unfinished and can be confusing for new users. A lot of the basic features are either duplicated or have some variety of "beta" state around them, which makes them more difficult to use than needed (especially for first time users).