solidus
🛒 Solidus, the open-source eCommerce framework for industry trailblazers.
Runssource: GitHubhomepageRubyBSD-3-Clausecommit 851dd5529326
Ruby, BSD-3-Clause licensed. The project labels itself: ecommerce, ecommerce framework, ecommerce platform, hacktoberfest, rails, ruby, solidus and storefront.
solidus runs. An Argusic agent installed it in 28 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Ruby 3.2.3 extracted from debs, bundler installed, all 202 gem dependencies resolved, URI::RFC2396_PARSER patched for Rails 8.1 compatibility, and core/order (246 passed), sample (2 passed), and API (97 passed, 2 pending) RSpec test suites all run with zero failures against SQLite in-memory database.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Ruby 3.2 missing from container7 minutes
- Native extensions failed: bindir and header paths pointed to /usr5 minutes
- URI::RFC2396_PARSER missing in Ruby 3.2 (needed by Rails 8.1)4 minutes
- Linker couldn't find libruby-3.2.so during extension builds3 minutes
- libyaml-0.so.2 missing for psych.so2 minutes
- bundle install re-failed due to cached failed builds2 minutes
- Install time
- 28 minutes
- Cold machine to finish
- 42 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- bundle exec rspec in core/models/spree/order_spec.rb (246 examples, 0 failures), sample/spec (2 examples, 0 failures), api/spec (97 examples, 0 failures, 2 pending)
- Model tokens used
- 472,197
- Exact commit tested
- 851dd5529326
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 120103ms:
Finished in 1 minute 22.96 seconds (files took 36.34 seconds to load)
97 examples, 0 failures, 2 pending
Randomized with seed 25774
Excellent results across the board.
Here's the final summary:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 28, "e…
tokens used
472,197
Excellent results across the board.
Here's the final summary:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 28, "e…Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 28 minutes.
- Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed BSD-3-Clause, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
ecommerceecommerce-frameworkecommerce-platformhacktoberfestrailsrubysolidusstorefront
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/solidus)Questions
- Does solidus run?
- Yes. solidus runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test solidus?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 851dd5529326. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test solidus?
- The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does solidus take to install?
- 28 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does solidus need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing solidus?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for solidus?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.