#NonprofitTech

🚀 Building in Public: A Year of Topher.Codes

🚀 Building in Public: A Year of Topher.Codes

2025 was a transformative year for Topher.codes, marked by bold technical upgrades, authentic storytelling, and a brand evolution that saw Ember the penguin embrace their inner phoenix. From navigating multi-generational Rails migrations and integrating real-world AI, to building a custom OAuth2 SSO and fostering a faith-tech community, this retrospective shares the victories, setbacks, and honest lessons learned along the way. Explore how building in public—transparently and vulnerably—sparked deeper connections and positioned Topher.codes as a unique bridge between technology and purpose.
Ember’s wisdom: Sometimes the only way to discover your phoenix wings is to molt your penguin feathers, one uncomfortable upgrade at a time. 🐧🔥

Deploying Rails 8 with Kamal 2: A Complete Guide

Deploying Rails 8 with Kamal 2: A Complete Guide

Rails 8 and Kamal 2 simplify deployment with zero-downtime, Docker-powered releases across platforms. This guide covers preparing code, building images, rolling deploys, secrets, rollbacks, health checks, and GitHub Actions integration. Plus, real-world lessons and a spiritual perspective on DevOps as trust and stewardship.

Building a Custom SSO: Why We Chose OAuth2 Over Devise

Building a Custom SSO: Why We Chose OAuth2 Over Devise

In 2021, we made a decision that seemed crazy: build our own OAuth2 Single Sign-On system instead of using Devise. Three years and three Rails upgrades later, that “crazy” decision looks like strategic foresight.

This is the story of Heis Soma—our custom authentication service powering Prayer Nook and positioning us to serve the broader Christian ministry ecosystem. It’s about architectural decisions, technical tradeoffs, and the surprising ways that following standards can future-proof your applications.

We built ~2,000 lines of OAuth2-compliant code. Survived Rails 6.1 → 8.0 with minimal changes. Achieved 10x performance improvements through Rails 7’s multiple database connections. Served 1,000+ users with zero security incidents.

Was it worth the 200-hour investment? Yes—but not for everyone. Here’s when custom authentication makes sense, when it doesn’t, and what we learned from three years in production.

Stay Updated with Topher Codes