Solidus: a published default password, and a sample-data command and asset path that still carry the upstream name
🛒 Solidus, the open-source eCommerce framework for industry trailblazers.
At a glance
- What is it?
- Solidus is an e-commerce framework for Ruby on Rails, forked from another one years ago and still visibly carrying it. The readme documents four gems, a live demo, published default admin credentials, a development container that starts two databases with the password spelled password, and a Turbolinks optimisation that comes with an explicit warning. The most useful details are the seams.
- Who is it for?
- Solidus fits a team that wants the whole storefront, admin and API rather than assembling them, and the four-gem split means you can take only the core and build your own front end if you would rather. Three things to weigh.
- Can I use it commercially?
- Yes. BSD-3-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 3 days ago.
- What is it written in?
- Mainly Ruby, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- solidusio/solidus5,348 ★ · +15
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| solidusio/solidus | 5.3k | 5.3k |
15 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Two maintained lines shipped on the same afternoon
The three most recent releases are v4.8.0 on 2026-10-09 and two releases of the admin gem, solidus_admin/v0.4.1 on 2026-10-07 and solidus_admin/v0.5.0 on 2026-10-14. There is also a configuration file at the repository root for a tool that automates backporting fixes into release branches. The readme also offers a third path for people who want the newest code, by pointing the gem at the repository rather than the packaged release, and follows it immediately with the warning that the branch is not guaranteed ever to be in a fully functioning state and is too risky for production. One small inconsistency sits inside that warning: it names the branch as master, while the repository's default branch is called main.
Two documented commands still carry the upstream project's name
This is a fork, and the readme does not hide where the seams are. The sample data is loaded by a rake task under the upstream name, not this project's name, so the command you run to populate a development database with products calls a namespace that does not match the gem you installed. The same is true of the asset manifest: the Turbolinks instructions tell you to edit a file under a directory named for the other project, inside a path that begins with a vendor assets directory. Both are functional instructions rather than historical references, so anyone following the readme will type the upstream paths. The file listing shows the same split structurally, with a promotions directory and a separate directory holding legacy promotions code.
The default admin credentials are printed in the readme and next to a live demo
There is a section whose entire content is the default email address and password for the admin account, given as a literal example address and a short test password, and it sits further down the readme than the link to a live demonstration store. The section exists for a good reason, since the install steps ask you to choose an admin email and password as part of setting the application up, and the readme is telling you what you will get if you skip that. The instruction to set your own during installation is the mitigation, and it is only an instruction.
One company is named as the main code contributor and director
The funding section is unusually direct about governance for an open source project. It says the project relies on funds and time donated by developers and stakeholders, it asks for backing through an open collective, and then it names a single company as the present main code contributor and director, crediting it with technical guidance and with coordinating community efforts and activities. That is a candid statement of stewardship rather than a claim of neutrality, and the repository reflects it: a governance document sits at the root. The rest of the section is a programme rather than a structure. Ambassadors get their logo and a link on the readme through the same funding platform, one ambassador is shown as an example, and there is a separate mailing list for reporting security problems.
Four gems, and the one most people want is the smallest
Requiring the main gem installs four of them: a RESTful API, an admin area, a core of models, mailers and classes, and a package of sample data. The readme then says something that is really an invitation to build your own front end, namely that you may only want the core and combine it with your own custom front end, admin interface and API. That single sentence is the difference between this project and a packaged store, and it is why the sample data lives in its own gem: a production installation does not need it. The sample package is a real sub-project with its own licence, readme, rake tasks, database directory, library directory and gemspec, and the class documentation plus a guides site are where the rest of the detail lives.
The development container runs two databases with the password spelled password
The compose file is the most detailed artefact in the repository and it describes a sandbox rather than a deployment. It starts a MySQL server and a PostgreSQL server at the same time, both with credentials that are the word password, and passes both host variables plus a flag meaning all databases into the application service, so you choose one without editing the file. The MySQL service additionally sets a command-line flag naming the older authentication plugin. The application image is built from a directory of its own with the interpreter, the Node version, both database versions and the bundler version passed in as build arguments, and it is tagged with a development version that reads four point nine, one minor version ahead of the newest release, four point eight. Its command installs the bundle, prints a line telling you to read the readme, and then parks on a null device to stay alive, with a shared memory size set for browser-driven tests.
Three linters, a documented performance fix and an optimisation with a warning
Style tooling is configured four ways at the root: a linter with its own configuration, the same linter's exception file which is where accepted debt accumulates, a second formatter's configuration, and a JavaScript linter configuration for the asset pipeline. There is also a file listing template files the formatter should skip and a list of revisions excluded from blame, which is how a project absorbs large mechanical reformats without burying real history. The performance section contains the kind of advice that only appears in a project with many contributors: development mode loads every style and script file separately, and one line in the development environment configuration turns that off:
config.assets.debug = falseThe last section is the most interesting, because it recommends an optimisation for the admin area and then warns that it can break extensions and customisations, at your own risk, immediately after telling you which file to edit.
Editorial conclusion
Solidus fits a team that wants the whole storefront, admin and API rather than assembling them, and the four-gem split means you can take only the core and build your own front end if you would rather. Three things to weigh. The readme publishes default admin credentials and links a live demo's admin area, so treat any installation you expose as compromised until you have changed them, and the install steps do ask you to. A documented command and an asset path still use the upstream project's naming, which tells you the fork is thorough but not finished. And the development compose file runs two database servers simultaneously with trivial credentials, which is convenient for a sandbox and would be indefensible anywhere else.
Frequently asked questions
What is Solidus?
A free, open-source e-commerce platform built on Ruby on Rails and forked from another Rails store. Requiring the main gem installs four of them: a RESTful API, an admin area, a core of models, mailers and classes, and a package of sample data. The readme notes you may want only the core and bring your own front end, admin and API.
How do I run Solidus locally?
Install an image processing tool first, because the file attachment library requires it. Then either run the setup script, optionally setting a database environment variable to choose PostgreSQL or MySQL, since those gems are installed through it, or bring up the compose stack, which starts both database servers and the application together with a shared port for the storefront.
What is the default admin login for Solidus?
The readme prints a default email address and a short test password, and notes that the installation steps ask you to set your own combination. Separately, the readme's Demo section links a live demonstration store and its admin area.
How do I install a development version of Solidus?
By pointing the gem at the repository instead of the packaged release. The readme warns immediately afterwards that this branch is not guaranteed ever to be in a fully functioning state and is too risky to use in production.
Does Solidus still contain code from the project it was forked from?
Yes, in documented places. The command that loads sample data is under the upstream project's name, the instructions for enabling a faster admin area tell you to edit an asset manifest under an upstream directory.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/solidusio-solidus)Star history chart for your README
[](https://hysenlabs.com/projects/solidusio-solidus)Was this useful?