OpenSourceRails

OpenSourceRails started because I kept asking the same question: what do real Rails apps actually look like? Tutorials get you so far, but at some point you need to see how production applications handle complexity. Most open-source Rails projects are abandoned experiments, course exercises, or so over-engineered they confuse more than they help. I wanted a place that filtered for quality.

The site scraped GitHub to catalog what gems projects used, what frontend stacks they chose, how their app directories were structured, and when they last showed signs of life. When a project got added, a chain of background workers ran through GitHub’s API—grabbing stars, parsing Gemfiles, walking directory structures, categorizing everything into frontend and backend buckets. All of it ran periodically to keep the data fresh without hammering rate limits.

There was a comparison tool too. Upload your Gemfile.lock and see how your choices stacked up against indexed projects. Each gem got ranked from dubious to popular based on usage across the catalog. Not gospel—plenty of solid gems are niche—but useful for spotting outliers.

The operating model was simple. I’d find repos on GitHub, scan them via a bookmarklet, clean up names and add logos in the admin panel. Scraping handled the grunt work; curation was the bottleneck. Always is.

Eventually I stopped maintaining it. The domain lapsed, someone else grabbed it, and now it’s gone. The code’s still on GitHub if anyone wants to resurrect the idea.