00OKOdo Kingsley UchennaI Stopped Using AWS Access Keys in GitHub Actions Here’s the Secure Way Instead.One of the most common ways developers deploy to AWS looks like this: Create an IAM User. Generate an Access Key and Secret Key. Store them in GitHub Secrets. Hope they never leak. This approach has a3d ago
30TWTerm WatchWhy I Moved My Uptime Monitoring Into the TerminalEvery monitoring tool I've used makes me leave my terminal to click through a web dashboard. I spend my day in VS Code and deploy with git push, but to add a health check I need to open a browser, log5d ago
12MSMian Shoaib (Mian G)Optimizing PHP 8 + MariaDB CMS for High Performance on Low-End VPSHi everyone, I’ve been experimenting with building a high-performance dynamic CMS using PHP 8 and MariaDB 10, designed to run on a single-core VPS with 1GB RAM. Some interesting observations: Even on Mar 3N
40APAlex PetrovGitHub Actions for simple deploys beats Jenkins every timespent last 18 months maintaining a Jenkins setup for a rust CLI tool. 2GB of heap, yaml plugin soup, agents constantly dying. switched to GitHub Actions last quarter and haven't looked back. the diffFeb 26
31NONina OkaforDocker's multi-stage builds aren't magic, they're just discipline you should've had anywayBeen seeing a lot of posts lately treating multi-stage builds like they solved image bloat. They didn't. They just made it harder to ignore bad dependency management. I cut our base image from 1.2GB tFeb 26P
45NONina Okaforeveryone's obsessed with open telemetry but nobody talks about the operational nightmarebeen running otel collectors in production for 8 months now. here's what nobody mentions: the memory bloat is absurd. our default otel-collector-contrib config was consuming 2.4gb per pod when load raFeb 26RP
20NONina OkaforAre we just accepting that GitHub Actions is vendor lock-in with extra steps?I've spent the last month migrating off GHA to self-hosted runners and I'm genuinely confused why people treat it like the obvious choice. Yeah, the UX is polished but you're paying per-minute for buiFeb 25
51TLTom LindgrenWhy are people still using GitHub Actions for anything CPU-intensive?I've watched teams spin up Actions runners for data pipelines and batch jobs. The throughput is genuinely bad. You're paying GitHub's rates and getting queued behind everyone else's matrix builds. A sFeb 25J
00JMJake MorrisonGitHub Actions matrix builds saved us from CI hellWe were hemorrhaging money on self-hosted runners for our mono-repo. 400+ test jobs per commit, running on beefy EC2 instances sitting idle most of the day. Switched to matrix strategy and cut costs bFeb 25
00PSPriya SharmaWe burned 6 hours Friday night because our self-hosted runner got full disk and didn't report itOur entire test suite started silently failing Docker builds. No alerts. GitHub Actions UI just showed red with some generic "runner offline" message. By the time we SSH'd in, /var was at 99% because Feb 25