Part 12 of this project

Deploy

Prepare Cobblecart Market for production hosting.

Goal

This snapshot advances Cobblecart Market by teaching you to prepare Cobblecart Market for production hosting.

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

Production needs HTTPS cookies, a strong secret, env-only database URLs, built assets, and forced migrations.

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

Walkthrough

Review deploy docs; never commit secrets.

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

bin/rails db:migrate
bin/rails server -b 0.0.0.0 -p ${PORT:-3010}

Run and verify

Enter 12-Deploy, 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/12-Deploy
bundle install
npm install
cp .env.example .env
bin/rails db:prepare
bin/rails server -b 0.0.0.0 -p 3010

Troubleshooting

If sessions vanish after deploy, check HTTPS cookie and domain settings.

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

List every secret that must live only in the host environment.

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