Tech

Recently, I have been working on a Sinatra-based web app. Some backend pages were designed using Tailwind CSS, which meant I needed to compile Tailwind assets after every change. I was deploying the API using Kamal, and every time I deployed, I had to run the Tailwind build command manually: bundle exec rake tailwind:build This quickly became tedious, especially when deploying frequently during development. Automating with Post-Deploy Hooks I wanted to automate this process so that Tailwind assets are built automatically after every deployment. After digging a bit, I discovered post-deploy hooks in Kamal. ...

🚨 The Problem Everything worked fine locally—but CI kept failing. I was working on a Rails application that used two databases: A primary database (fully controlled by the app) A secondary database (owned by a different application) Here’s the catch: 👉 The secondary database was read-only from my app’s perspective. Locally, this wasn’t an issue because the database already existed and had the expected schema. But in CI: The secondary database didn’t exist Rails tried to interact with it like a normal DB Tests failed with missing tables and connection errors 🔍 Root Cause The issue came down to this: ...

After ages of procrastination for building a portfolio site, I finally reached a breaking point. One day, I dove deep into researching Static Site Generators (SSGs) to find a workflow that wouldn’t feel like a chore. I landed on Hugo for its speed and simplicity. After hours of searching through themes, I selected PaperMod for its simple, clean, and clear design. It was exactly what I needed: a site that stays out of the way and lets the content speak for itself. ...