marckohlbrugge

The Unofficial 37signals/DHH Rails Style Guide

About This Document

This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.

Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.

How this was created: Claude Code analyzed the entire codebase - routes, controllers, models, concerns, views, JavaScript, CSS, tests, and configuration. The goal was to extract not just what patterns are used, but why - inferring philosophy from implementation choices.

peterc

• You MUST NOT try and generate a Rails app from scratch on your own by generating each file. For a NEW app you MUST use rails new first to generate all of the boilerplate files necessary.
• Create an app in the current directory with rails new .
• Use Tailwind CSS for styling. Use --css tailwind as an option on the rails new call to do this automatically.
• Use Ruby 3.2+ and Rails 8.0+ practices.
• Use the default Minitest approach for testing, do not use RSpec.
• Default to using SQLite in development. rails new will do this automatically but take care if you write any custom SQL that it is SQLite compatible.
• An app can be built with a devcontainer such as rails new myapp --devcontainer but only do this if requested directly.
• Rails apps have a lot of directories to consider, such as app, config, db, etc.
• Adhere to MVC conventions: singular model names (e.g., Product) map to plural tables (products); controllers are plural.
• Guard against incapable browsers accessing controllers with `allo

rameerez

#!/bin/bash

# Production Docker Host Hardening Script v2
# For Ubuntu Server 24.04 LTS (Noble)
# Suitable for both Kamal deployment and builder hosts

set -euo pipefail
IFS=$'\n\t'

# --- Constants ---

danielpclark

At the moment upgrading vue-loader causes some changes in how things are done. These are my config options for these items just to get it working.

config/webpack/environment.js

const { environment } = require('@rails/webpacker')
const coffee = require('./loaders/coffee')
const vue = require('./loaders/vue')

environment.loaders.append('vue', vue)

santisbon

Enter this in the search box along with your search terms:

Get all gists from the user santisbon.
user:santisbon

Find all gists with a .yml extension.
extension:yml

Find all gists with HTML files.
language:html

RobertoBarros

git fetch origin
git reset --hard origin/master

# https://stackoverflow.com/questions/1628088/reset-local-repository-branch-to-be-just-like-remote-repository-head

# Remove untracked files:
git clean -f


# Undo merge with conflicts

lfender6445

Pry Cheat Sheet

• Youtube Tutorial 2013

Command Line

• pry -r ./config/app_init_file.rb - load your app into a pry session (look at the file loaded by config.ru)
• pry -r ./config/environment.rb - load your rails into a pry session

Debugger

blacktm

#!/bin/bash

# --------------------------------------------------------------------------------------------
# Installs Ruby using rbenv/ruby-build on the Raspberry Pi (Raspbian)
#
# Run from the web:
#   bash <(curl -s https://gist.githubusercontent.com/blacktm/8302741/raw/install_ruby_rpi.sh)
# --------------------------------------------------------------------------------------------

# Set the Ruby version you want to install

henrik

class BigDecimal
  def inspect
    format("#<BigDecimal:%x %s>", object_id, to_s('F'))
  end
end

nbibler

if [ -f "$rvm_path/scripts/rvm" ]; then
  source "$rvm_path/scripts/rvm"

  if [ -f ".rvmrc" ]; then
    source ".rvmrc"
  fi

  if [ -f ".ruby-version" ]; then
    rvm use `cat .ruby-version`
  fi