- Join our Slack
- Join us in New York City on June 28-29th for OpenCommerce Conf 2016
- 2016 Development Roadmap
- Vote & comment on roadmap features
Spree is a complete open source e-commerce solution built with Ruby on Rails. It was originally developed by Sean Schofield and is now maintained by developers from Spark Solutions and Vinsol. We're open to contributions and accepting new Core Team members.
Spree consists of several different gems, each of which are maintained in a single repository and documented in a single set of online documentation.
- spree_api (RESTful API)
- spree_frontend (Customer frontend)
- spree_backend (Admin panel)
- spree_cmd (Command-line tools)
- spree_core (Models & Mailers, the basic components of Spree that it can't run without)
- spree_sample (Sample data)
rails (~> 4.2.6)
Add Spree gems to your Gemfile:
gem 'spree', '~> 3.1.0.rc1' gem 'spree_auth_devise', '~> 3.1.0.rc1' gem 'spree_gateway', '~> 3.1.0.rc1'
Use the install generators to set up Spree:
rails g spree:install --user_class=Spree::User rails g spree:auth:install rails g spree_gateway:install
Alternatively, if you want to use the bleeding edge version of Spree, add this to your Gemfile:
gem 'spree', github: 'spree/spree' gem 'spree_auth_devise', github: 'spree/spree_auth_devise' gem 'spree_gateway', github: 'spree/spree_gateway'
Note: The master branch is not guaranteed to ever be in a fully functioning state. It is unwise to use this branch in a production system you care deeply about.
By default, the installation generator (
rails g spree:install) will run
migrations as well as adding seed and sample data. This can be disabled using
rails g spree:install --migrate=false --sample=false --seed=false
You can always perform any of these steps later by using these commands.
bundle exec rake railties:install:migrations bundle exec rake db:migrate bundle exec rake db:seed bundle exec rake spree_sample:load
Browse Admin Interface
config.assets.debug = false
Spree is meant to be run within the context of Rails application and the source code is essentially a collection of gems. You can easily create a sandbox application inside of your cloned source directory for testing purposes.
Clone the Git repo
git clone git://github.com/spree/spree.git cd spree
Install the gem dependencies
Create a sandbox Rails application for testing purposes which automatically perform all necessary database setup
bundle exec rake sandbox
Start the server
cd sandbox rails server
We use CircleCI to run the tests for Spree.
You can see the build statuses at https://circleci.com/gh/spree/spree.
Each gem contains its own series of tests, and for each directory, you need to do a quick one-time creation of a test application and then you can use it to run the tests. For example, to run the tests for the core project.
cd core bundle exec rake test_app bundle exec rspec spec
If you would like to run specs against a particular database you may specify the dummy apps database, which defaults to sqlite3.
DB=postgres bundle exec rake test_app
If you want to run specs for only a single spec file
bundle exec rspec spec/models/spree/state_spec.rb
If you want to run a particular line of spec
bundle exec rspec spec/models/spree/state_spec.rb:7
You can also enable fail fast in order to stop tests at the first failure
FAIL_FAST=true bundle exec rspec spec/models/state_spec.rb
If you want to run the simplecov code coverage report
COVERAGE=true bundle exec rspec spec
If you're working on multiple facets of Spree to test, please ensure that you have a postgres user:
createuser -s -r postgres
And also ensure that you have PhantomJS installed as well:
brew update && brew install phantomjs
To execute all the tests, you may want to run this command at the root of the Spree project to generate test applications and run specs for all the facets:
Spree is an open source project and we encourage contributions. Please review the contributing guidelines before contributing.
In the spirit of free software, everyone is encouraged to help improve this project.
Here are some ways you can contribute:
- by using prerelease versions / master branch
- by reporting bugs
- by translating to a new language
- by writing or editing documentation
- by writing specs
- by writing needed code or finishing code
- by refactoring code
- by reviewing pull requests
- by verifying issues
Spree is released under the New BSD License.