Below you will find pages that utilize the taxonomy term “GCP”
GitHub Actions for AWS, Azure and GCP
I’m abandoning the multi-cloud blog hosting model that I was using in favor of AWS Amplify to simplify TLS configuration. But I thought I should document the old approach a little further in case I ever go back to it.
The build pipeline for my blog fails every once in a while. For example, there was an issue with the Azure CLI earlier this month. Each time that happens it takes me a few minutes to remember how the pipeline works. Therefore, I am documenting it quickly in this post.
Cloud Storage and Trailing Slashes
Cloud Storage and Trailing Slashes
Shortly after configuring this site to be served simultaneously from AWS, Azure and GCP, I realize I had a bug. Occasionaly the images were not loading. Ironically this was only happening on the Multi-Cloud Blogging post. After some investigation, I found this caused by how various providers handle a URI without a trailing slash. Specifically Azure.
The Issue
When I render the footer of this blog, I include the name of the cloud provider that served the page. I also include a link to the post describing how it’s all configured. When I created that link, I left off the trailing slash in the URI. For example http://blog.brianbeach.com/posts/2019-12-30-multi-cloud-blog.
Multi-Cloud Blogging
I spent some time over Thanksgiving moving my blog from Blogger to Hugo. I have been hosting my site in an Amazon S3 bucket with an automated build in AWS CodeBuild. That has been running well for the past month and I have worked out most of the kinks. So, I decided to make my blog Multi-Cloud and host it on AWS, Azure, and GCP while load balancing traffic across the three platforms. The footer at the bottom of each page will tell you where the page is served from. I also moved the build process to GitHub Action so I was not dependent on AWS for continuous integration.