<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://andypowell00.github.io/</id><title>AP Coding</title><subtitle>Blog of a programmer, mostly C#, AI, APIs, and other fun discoveries for my reference and others.</subtitle> <updated>2025-03-07T14:26:07-05:00</updated> <author> <name>Andy Powell</name> <uri>https://andypowell00.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://andypowell00.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://andypowell00.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2025 Andy Powell </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Using Redis for a cache with a Next.JS app</title><link href="https://andypowell00.github.io/posts/Redis-NextJS/" rel="alternate" type="text/html" title="Using Redis for a cache with a Next.JS app" /><published>2025-01-30T15:21:59-05:00</published> <updated>2025-01-30T15:21:59-05:00</updated> <id>https://andypowell00.github.io/posts/Redis-NextJS/</id> <content src="https://andypowell00.github.io/posts/Redis-NextJS/" /> <author> <name>Andy Powell</name> </author> <category term="nextjs" /> <category term="redis" /> <category term="cache" /> <category term="vercel" /> <summary> Migrating from unstable_cache to Redis in Next.js Why Redis? When deploying Next.js applications on Vercel, the built-in unstable_cache can be unreliable. Redis provides a more robust caching solution with several advantages: Persistent storage across server restarts and deployments Configurable Time-To-Live (TTL) for cache entries Reliable performance at scale Consistent behavior a... </summary> </entry> <entry><title>Utilizing fail2ban on Lightsail Wordpress Site</title><link href="https://andypowell00.github.io/posts/Fail2Ban-Wordpress/" rel="alternate" type="text/html" title="Utilizing fail2ban on Lightsail Wordpress Site" /><published>2025-01-30T15:21:59-05:00</published> <updated>2025-01-30T15:21:59-05:00</updated> <id>https://andypowell00.github.io/posts/Fail2Ban-Wordpress/</id> <content src="https://andypowell00.github.io/posts/Fail2Ban-Wordpress/" /> <author> <name>Andy Powell</name> </author> <category term="wordpress" /> <category term="php" /> <category term="aws" /> <summary> Securing Your WordPress Site on AWS Lightsail with Fail2Ban Introduction Fail2Ban is a powerful intrusion prevention tool that helps protect your server from brute-force attacks by monitoring log files and temporarily banning IP addresses that show malicious behavior. We ran into an increase of bot activity on a particular site, which lead me to start researching some extra ways to mitigate ... </summary> </entry> <entry><title>Setting up a simple Azure DevOps Pipeline</title><link href="https://andypowell00.github.io/posts/Azure-Pipeline/" rel="alternate" type="text/html" title="Setting up a simple Azure DevOps Pipeline" /><published>2025-01-15T15:21:59-05:00</published> <updated>2025-01-15T15:21:59-05:00</updated> <id>https://andypowell00.github.io/posts/Azure-Pipeline/</id> <content src="https://andypowell00.github.io/posts/Azure-Pipeline/" /> <author> <name>Andy Powell</name> </author> <category term="azure" /> <category term="devops" /> <category term="cicd" /> <category term="dotnet" /> <summary> Migrating from GitHub Actions to Azure DevOps Pipelines for .NET Deployment   Recently, I transitioned my .NET Core API deployment from GitHub Actions to Azure DevOps Pipelines. While the process seemed straightforward at first, I ran into a few challenges—particularly around self-hosted agents, deployment methods, and ensuring my API was properly updated.   In this post, I’ll walk through th... </summary> </entry> <entry><title>Adding Unit Tests to Azure Pipeline</title><link href="https://andypowell00.github.io/posts/Unit-Tests-Azure-Pipeline/" rel="alternate" type="text/html" title="Adding Unit Tests to Azure Pipeline" /><published>2024-12-12T15:21:59-05:00</published> <updated>2024-12-12T15:21:59-05:00</updated> <id>https://andypowell00.github.io/posts/Unit-Tests-Azure-Pipeline/</id> <content src="https://andypowell00.github.io/posts/Unit-Tests-Azure-Pipeline/" /> <author> <name>Andy Powell</name> </author> <category term="development" /> <category term="azure" /> <summary> Adding Unit Tests to Your Azure DevOps Pipeline Looking to make my Azure DevOps pipeline more efficient, I wanted to start with just auto running my Unit Tests by adding a task that focuses on running dotnet test in the build stage before deployment. Updating azure-pipelines.yml Below is an updated azure-pipelines.yml file: trigger: branches: include: - main # Runs on main branc... </summary> </entry> <entry><title>Creating a New Collection with TTL in Cosmos MongoDB</title><link href="https://andypowell00.github.io/posts/CosmosDB-Azure/" rel="alternate" type="text/html" title="Creating a New Collection with TTL in Cosmos MongoDB" /><published>2024-12-12T13:00:00-05:00</published> <updated>2024-12-12T13:00:00-05:00</updated> <id>https://andypowell00.github.io/posts/CosmosDB-Azure/</id> <content src="https://andypowell00.github.io/posts/CosmosDB-Azure/" /> <author> <name>Andy Powell</name> </author> <category term="azure" /> <category term="cosmosdb" /> <category term="mongodb" /> <summary> When working on my dashboard application, I needed to set up a new collection in Cosmos DB using the MongoDB API. One important feature I wanted was a Time to Live (TTL) policy for documents, ensuring automatic expiration after 35 days. I was looking into just writing a script, but this seemed like the best way forward. The TTL does not affect existing documents, so you either have to do an u... </summary> </entry> </feed>
