Part 6 of this project

Registration

Validate customer accounts and store password hashes.

Goal

This snapshot advances Cobblecart Market by teaching you to validate customer accounts and store password hashes.

Every numbered folder is a complete app. Run this stage independently, then compare it with the previous folder.

Prerequisites

Use Ruby 3.2+, Bundler, Node.js 20+, and Docker for Postgres stages.

Port 3010 must be free. Copy .env.example before database stages.

  • Ruby and Bundler
  • Node.js and npm
  • Docker from part 4 onward

Concepts

Registration normalizes email, enforces uniqueness, hashes passwords, signs the user in, and regenerates the session.

Turbo keeps interactive UI on the server; Tailwind styles the storefront; Active Record owns persistence and authorization checks.

Walkthrough

Build a registration form with CSRF-safe posts and validation errors.

Read the example, then open the matching snapshot. The repository includes validation, CSRF, and the surrounding structure.

user = User.create!(user_params)
reset_session
session[:user_id] = user.id
redirect_to root_path

Run and verify

Enter 06-Registration, bundle install, copy .env.example, migrate, seed, and boot Puma on port 3010.

Open http://127.0.0.1:3010. From data lessons onward, Ada and Grace use password123.

docker compose up -d
git clone https://github.com/michaeldunga1/fcc-rails-ecommerce.git
cd fcc-rails-ecommerce/06-Registration
bundle install
npm install
cp .env.example .env
bin/rails db:prepare
bin/rails server -b 0.0.0.0 -p 3010

Troubleshooting

Duplicate email and password confirmation failures should redisplay field errors.

For database failures, confirm Docker and the cobble_NN name. Never commit .env, vendor/bundle, or node_modules.

  • Read the first exception first
  • Rebuild assets after Tailwind class changes
  • Never commit secrets

Try this

Try a short password, mismatched confirmation, and a duplicate email.

Test a happy path and one invalid or unauthorized request.

  • Make one small change
  • Test it in the browser
  • Compare with the next snapshot only after it works