Registration

Goal

This snapshot advances Junction Almanac by teaching you to register users with validated, hashed passwords.

Every numbered folder is a complete Rails application. Run this stage independently, then compare it with the previous snapshot to isolate the new responsibility.

Prerequisites

Use Ruby 3.1 or newer, Bundler, PostgreSQL through Docker, and a terminal. Basic Ruby, HTML, and SQL vocabulary will make the framework conventions easier to recognize.

The app listens on port 3000. PostgreSQL is exposed on host port 5434, and every snapshot names a different database so lesson data never leaks between stages.

• Ruby and Bundler
• Docker with Compose
• A code editor and terminal

Concepts

has_secure_password adds password assignment, confirmation validation, and secure authentication while storing only a bcrypt digest.

Keep the Rails request path visible: the router selects a controller action, Active Record handles data rules, and an ERB view renders the response inside the shared layout.

Walkthrough

Permit only email and password fields, normalize email addresses, render validation errors with status 422, and redirect after a successful POST.

Read the focused example, then inspect the matching repository snapshot for the surrounding configuration, validation, failure paths, and accessible markup.

@user = User.new(params.require(:user).permit(:email, :password, :password_confirmation))
if @user.save
  redirect_to root_path, notice: "Account created."
end

Run and verify

Enter 06-Registration, install its bundle, prepare its database when this stage uses one, and start Rails on port 3000.

Open http://localhost:3000. Keep the server log visible so you can connect each browser action to its route, SQL query, rendered view, redirect, or validation error.

git clone https://github.com/michaeldunga1/fcc-rails-blog.git
cd fcc-rails-blog/06-Registration
docker compose -f ../docker-compose.yml up -d
bundle install
bin/rails db:prepare db:seed
bin/rails server -p 3000

Troubleshooting

A form rendered with status 200 after validation failure can confuse clients and tests; return :unprocessable_entity. Duplicate emails must be blocked by both model validation and a unique index.

If Rails reports a missing table, run bin/rails db:prepare db:seed in the current snapshot. Connection failures usually mean PostgreSQL is stopped or port 5434 is already occupied.

• Read the first exception first
• Confirm the current numbered folder
• Never commit secrets or config/master.key

Try this

Submit mixed-case email, mismatched passwords, a short password, and an existing address.

Test one successful request and one invalid or unauthorized request. A production-minded Rails app must preserve data rules even when someone bypasses the visible links and submits a direct request.

• Make one focused change
• Verify it in the browser
• Move on only after the checkpoint works