I've been working on a Blog Application built with Ruby on Rails to practice backend architecture, clean code standards, and Rails idioms.
I'm sharing the repository to get feedback, code reviews, and suggestions on how to make the codebase cleaner and more scalable.
🚀 Tech Stack & Features
- Backend: Ruby on Rails 7, PostgreSQL
- Features: User authentication, post publishing, commenting system, dynamic permissions
🛠️ GitHub Repository
Blog-App
A robust blogging platform built with Ruby on Rails and PostgreSQL.
Tech stack
- Ruby (>= 3.x)
- Rails (>= 8.x)
- PostgreSQL
- JavaScript (importmap / optional Node build tooling)
- TailwindCSS, Stimulus, Devise, Stripe
Quickstart (local development)
- Clone the repo
git clone https://github.com/sohamchavan07/Blog-App.git
cd Blog-App
- Install dependencies
bundle install
bin/setup || (yarn install || npm install)
- Environment
Copy example env and add required keys (Stripe keys, DB URL, secrets):
cp .env.example .env
# edit .env and add STRIPE_* and other secrets
- Database
rails db:create db:migrate db:seed
- Start the app
bin/dev
# or: rails server
Tests
Run the test suite with:
bin/rails test
# or if using RSpec: bundle exec rspec
Common commands
- Install gems:
bundle install - Install JS deps:
yarn installornpm install - Run migrations:
rails db:migrate - Seed:
rails db:seed - Start dev server:
bin/devorrails server
Screenshots
Environment variables (examples)
-
DATABASE_URLor standardconfig/database.ymlsettings -
RAILS_MASTER_KEYorconfig/master.key - …
🔍 Where I'm Looking for Feedback
- Controller vs Model Boundaries: Are controllers thin enough, or am I leaning on the wrong layer for business logic?
- Database Performance: Any obvious N+1 queries or missing indexes on foreign keys?
- Rails Conventions: Code smells or areas where I can better follow "Convention over Configuration"?
I’d love any constructive feedback, refactoring ideas, or suggestions on what to build next. Drop your thoughts below!
Source: DEV Community


