Template for starting Rails apps on the pal-e platform. No local Ruby needed.
Remove references to nonexistent templates/ directory and Dockerfile.dev. The actual workflow pulls ruby-rails-build from Harbor via docker-compose with no per-project Dockerfile needed. Simplify Mermaid diagram and steps to match. Remove dead links to unwritten docs. Closes #1 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| docs | ||
| .gitignore | ||
| docker-compose.yml | ||
| README.md | ||
rails-base
Template for starting Rails apps on the pal-e platform. Copy the docker-compose.yml into a new repo and run rails new inside the container. No local Ruby required.
How It Works
There is no Dockerfile here. The docker-compose.yml pulls ruby-rails-build directly from Harbor — a pre-built image maintained in ldraney/base-images that includes Ruby 3.4.9, bundler, build tools, and PostgreSQL client libraries. Everything Rails needs is already in the image.
Your app code is volume-mounted into the container, so files generated by rails new appear in your local directory immediately. No rebuild when code changes. No per-project Dockerfile for dev.
Quick Start
mkdir ~/myapp && cd ~/myapp
cp ~/rails-base/docker-compose.yml .
docker compose run web rails new . -d postgresql --skip-ci --skip-kamal --skip-docker --skip-thruster --skip-action-text
docker compose up
Docs
| Doc | What it covers |
|---|---|
| Starting a New Project | Full walkthrough with Mermaid diagram |
| Multi-Database Architecture | Solid Cache/Queue/Cable — dev uses one DB, prod uses four |
Related Repos
ldraney/base-images— Ruby 3.4.9-slim Docker images on Harborldraney/ror-css-guide— Plain CSS conventions for Rails + Hotwire