<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure on Gene Reader</title><link>https://blog.gereader.xyz/categories/infrastructure/</link><description>Recent content in Infrastructure on Gene Reader</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>eugene.reader@gmail.com (Gene Reader)</managingEditor><webMaster>eugene.reader@gmail.com (Gene Reader)</webMaster><lastBuildDate>Sat, 11 Oct 2025 09:05:21 -0700</lastBuildDate><atom:link href="https://blog.gereader.xyz/categories/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>Part 1 - Building a CI/CD Pipeline with GitHub Actions and Container Registries</title><link>https://blog.gereader.xyz/posts/part-1-cicd-container-registry/</link><pubDate>Mon, 18 Aug 2025 15:10:14 -0700</pubDate><author>eugene.reader@gmail.com (Gene Reader)</author><guid>https://blog.gereader.xyz/posts/part-1-cicd-container-registry/</guid><description>&lt;h1 id="building-a-cicd-pipeline-with-github-actions-and-container-registries"&gt;Building a CI/CD Pipeline with GitHub Actions and Container Registries&lt;/h1&gt;
&lt;p&gt;I recently built a complete CI/CD pipeline for my Flask job application tracking app. Like my Hugo blog setup, I struggled to find a single source covering everything I needed. I found myself cobbling together multiple YouTube videos, tutorials, and AWS and GitHub Actions documentation just to get a working pipeline. There&amp;rsquo;s a lot of moving parts here, so I decided to split this into a two-part series.&lt;/p&gt;</description></item><item><title>Part 2 - Deploying to AWS ECS: From Container Registry to Production</title><link>https://blog.gereader.xyz/posts/part-2-cicd-deploy-aws-ecs/</link><pubDate>Fri, 22 Aug 2025 15:10:14 -0700</pubDate><author>eugene.reader@gmail.com (Gene Reader)</author><guid>https://blog.gereader.xyz/posts/part-2-cicd-deploy-aws-ecs/</guid><description>&lt;h1 id="deploying-to-aws-ecs-from-container-registry-to-production"&gt;Deploying to AWS ECS: From Container Registry to Production&lt;/h1&gt;
&lt;p&gt;In &lt;a href="https://blog.gereader.xyz/posts/part-1-cicd-container-registry/"&gt;Part 1&lt;/a&gt;, I built a pipeline that automatically tests my Flask app and pushes containers to both GHCR and ECR. I&amp;rsquo;m going to deploy those containers somewhere that people can use them. I&amp;rsquo;m going to use AWS ECS to make my app publicly accessible. (This won&amp;rsquo;t be accessible to the public, I&amp;rsquo;ll be spinning this down after the demo to avoid burning through my AWS credits and racking up costs.)&lt;/p&gt;</description></item><item><title>Building a RSS News Aggregator with GitHub Pages</title><link>https://blog.gereader.xyz/posts/rss-news-aggregator/</link><pubDate>Sat, 11 Oct 2025 09:05:21 -0700</pubDate><author>eugene.reader@gmail.com (Gene Reader)</author><guid>https://blog.gereader.xyz/posts/rss-news-aggregator/</guid><description>&lt;p&gt;I find myself doom scrolling through content that an algorithm somewhere has decided I want to read. My browser&amp;rsquo;s &amp;ldquo;new tab&amp;rdquo; page often shows articles I don&amp;rsquo;t care about or don&amp;rsquo;t want to see. I realized I could take control by setting my own homepage. A page that shows the news I actually want to read, because I curated the list myself. I understand I could likely find an RSS reader website and build a feed that way, but this seemed like a simple enough problem that I should be able to do it myself without worrying about ads or algorithms.&lt;/p&gt;</description></item><item><title>Set Up Hugo Blog</title><link>https://blog.gereader.xyz/posts/set-up-hugo-blog/</link><pubDate>Sun, 17 Aug 2025 16:30:05 -0700</pubDate><author>eugene.reader@gmail.com (Gene Reader)</author><guid>https://blog.gereader.xyz/posts/set-up-hugo-blog/</guid><description>&lt;h1 id="setting-up-a-hugo-based-blog-on-github-pages"&gt;Setting Up a Hugo-based Blog on GitHub Pages&lt;/h1&gt;
&lt;p&gt;I will be showing you how I set up a Hugo blog, being published to GitHub Pages using GitHub Actions for free.&lt;/p&gt;
&lt;p&gt;I chose GitHub Pages because it offers the ability to host static websites for free with minimal configuration, and I have a new interest in GitHub Actions. I noted that the &amp;ldquo;modern&amp;rdquo; method to deploy a website on GitHub is with Actions and I couldn&amp;rsquo;t pass up the opportunity. While going through the process of deploying this blog, I found that no single resource had all the information I needed to get everything stood up. I figured, &amp;ldquo;hey I&amp;rsquo;m making a blog why not write what I wish I had&amp;rdquo; and that&amp;rsquo;s how this post came to be. The process is fairly simple from start to finish once you know where all the moving parts are located.&lt;/p&gt;</description></item></channel></rss>