-
ltc-devops-project
This is the sample application for the DevOps Capstone Project on Learn to Cloud. It shows your favorite TV Shows or movies, the front-end is in React and the API is written in Python using FastAPI. The goal is to get hands-on with DevOps practices like Containerization, CI/CD, IaC and monitoring.
Building and deploying a full-stack application involves more than just writing code. It's a journey through infrastructure, automation, and inevitable troubleshooting. As part of the Learn to Cloud initiative, I recently expanded on a previous Phase 2 Capstone Project (a Serverless Movies API) to focus on applying core DevOps practices like containerization, CI/CD, and eventually observability/monitoring. The target was a simple TV show application (a sample is available here. The path from local development to a containerized deployment on AWS using CI/CD was filled with valuable lessons. Here's a look at the experience, the hurdles, and how I overcame them.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
ltc-devops-project
This is the sample application for the DevOps Capstone Project on Learn to Cloud. It shows your favorite TV Shows or movies, the front-end is in React and the API is written in Python using FastAPI. The goal is to get hands-on with DevOps practices like Containerization, CI/CD, IaC and monitoring. (by richardatodo)
This project provided a rich learning experience across backend development, cloud database migration, containerization, EC2 instance management, and CI/CD automation within the “Learn to Cloud” framework. Encountering and solving issues with package management, security groups, environment variables, and IAM policies was invaluable. The application now runs on EC2, with deployments automated via GitHub Actions pushing to ECR. See repo here
-
Puts Debuggerer
Ruby library for improved puts debugging, automatically displaying bonus useful information such as source line number and source code.
Condition: Carefully crafting the sub claim condition to match the repo:ORG/REPO:ref... format, ensuring I didn't mistakenly include the https://github.com/ prefix. Getting the trust policy exactly right allowed the workflow to assume the role and push images to ECR successfully.