Table of Contents
- Key Stakeholders
- Getting Started
- Installation Options
- Developing Solidus
Thank you to all our donors! 🙏 Become a donor
Support this project by becoming a Key Stakeholder. Your logo will show up here with a link to your website. Become a Key Stakeholder
Solidus is a complete open source ecommerce solution built with Ruby on Rails. It is a fork of Spree.
Solidus consists of several gems. When you require the
solidus gem in your
Gemfile, Bundler will install all of the gems maintained in this repository:
solidus_frontend(Cart and storefront)
solidus_core(Essential models, mailers, and classes)
All of the gems are designed to work together to provide a fully functional
ecommerce platform. However, you may only want to use the
combine it with your own custom frontend, admin interface, and API.
Try out Solidus with one-click on Heroku:
Alternatively, you can use Docker to run a demo on your local machine. Run the following command to download the image and run it at http://localhost:3000.
docker run --rm -it -p 3000:3000 solidusio/solidus-demo:latest
To add solidus, begin with a Rails 5 application and a database configured and created. Add the following to your Gemfile.
gem 'solidus' gem 'solidus_auth_devise'
bundle command to install.
After installing gems, you'll have to run the generators to create necessary configuration files and migrations.
bundle exec rails g spree:install bundle exec rails g solidus:auth:install bundle exec rake railties:install:migrations
Run migrations to create the new models in the database.
bundle exec rake db:migrate
Finally start the rails server
bundle exec rails s
As part of running the above installation steps, you will be asked to set an admin email/password combination. The default values are
[email protected] and
The best way to ask questions is via the #support channel on the Solidus Slack.
Instead of a stable build, if you want to use the bleeding edge version of Solidus, use this line:
gem 'solidus', github: 'solidusio/solidus'
Note: The master branch is not guaranteed to ever be in a fully functioning state. It is too risky to use this branch in production.
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
There are also options and rake tasks provided by solidus_auth_devise.
You may notice that your Solidus store runs slowly in development mode. This
include. This can be disabled by adding the following to
config.assets.debug = false
To gain some extra speed you may enable Turbolinks inside of Solidus admin.
gem 'turbolinks', '~> 5.0.0' into your
Gemfile (if not already present) and append these lines to
CAUTION Please be aware that Turbolinks can break extensions and/or customizations to the Solidus admin. Use at own risk.
- Clone the Git repo
git clone git://github.com/solidusio/solidus.git cd solidus
- Install the gem dependencies
Solidus is meant to be run within the context of Rails application. You can easily create a sandbox application inside of your cloned source directory for testing purposes.
This sandbox includes solidus_auth_devise and generates with seed and sample data already loaded.
- Create the sandbox application
bundle exec rake sandbox
You can create a sandbox with PostgreSQL or MySQL by setting the DB environment variable.
DB=postgresql bundle exec rake sandbox
- Start the server
cd sandbox rails server
Solidus uses RSpec for tests. Refer to its documentation for more information about the testing library.
We use CircleCI to run the tests for Solidus as well as all incoming pull requests. All pull requests must pass to be merged.
You can see the build statuses at https://circleci.com/gh/solidusio/solidus.
Run all tests
ChromeDriver is required to run the frontend and backend test suites.
To execute all of the test specs, run the
bin/build script at the root of the Solidus project:
createuser --superuser --echo postgres # only the first time bin/build
bin/build script runs using PostgreSQL by default, but it can be overridden by setting the DB environment variable to
DB=mysql. For example:
env DB=mysql bin/build
If the command fails with MySQL related errors you can try creating a user with this command:
# Creates a user with the same name as the current user and no restrictions. mysql --user="root" --execute="CREATE USER '$USER'@'localhost'; GRANT ALL PRIVILEGES ON * . * TO '$USER'@'localhost';"
Run an individual test suite
Each gem contains its own series of tests. To run the tests for the core project:
cd core bundle exec rspec
rspec runs the tests for SQLite 3. If you would like to run specs
against another database you may specify the database in the command:
env DB=postgresql bundle exec rspec
Code coverage reports
If you want to run the SimpleCov code coverage report:
COVERAGE=true bundle exec rspec
In addition to core functionality provided in Solidus, there are a number of ways to add features to your store that are not (or not yet) part of the core project.
A list can be found at extensions.solidus.io.
If you want to write an extension for Solidus, you can use the solidus_cmd gem.
Solidus is an open source project and we encourage contributions. Please read CONTRIBUTING.md before contributing.