Spree Commerce Project

A Rails application powered by Spree Commerce.

Project flavors — detect FIRST, it changes every command

Not every Spree app is a create-spree-app project. Check these signals in order before running anything:

Signal	Flavor	How commands run
`backend/Gemfile` mentions spree + `docker-compose.yml` at root	create-spree-app project (5.4+)	`spree <cmd>` — the `@spree/cli` routes into the Docker `web` container
Rails app at root (`config/application.rb`, Gemfile with spree) + `docker-compose.yml` with a Spree image/build	spree-starter-style Docker app	`spree <cmd>` if the CLI resolves (`npx spree --version`); else `docker compose exec web <cmd>`
Rails app at root with spree gems, no Docker wiring	classic Rails app (typical pre-5.4)	Native, from the app root: `bin/rails …`, `bundle exec rake …`

Command mapping — Spree CLI form → classic-app native form: