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 37 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Solidus 4.8.0.dev installed with Ruby 3.3.13, all 203 gems installed, test suites run: admin (618 pass), promotions (1119 pass), legacy_promotions (792 pass), sample (2 pass), i18n (2 pass), core (4424 pass / 11 fail), api (647 pass / 11 fail), backend (760 pass / 6 fail)

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.20 (measured)
recorded runs
2
last tested
stars
5,349
forks
1,405
open issues
73
watchers
112
size
124 MB
created
last push

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.

Time lost to each failure while testing solidus, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Ruby not installed in container; required ruby >= 3.215 minutes
  • psych.so could not find libyaml at runtime during RDoc step of ruby build12 minutes
  • psych gem failed to compile during bundle install (missing libyaml)3 minutes
  • Bundle install failed because psych gem compilation couldn't find libyaml2 minutes
Install time
37 minutes
Cold machine to finish
41 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
bundle exec rspec across core (4435 examples), api (658), backend (766), admin (618), promotions (1119), legacy_promotions (792), sample (2), i18n (2), total 8390 examples across 8 test suites; 28 pre-existing failures in image attachment specs (ActiveStorage adapter nil.new bug) and manipulative query monitor (log format difference)
Model tokens used
586,937
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.

admin:    618 examples, 0 failures
promotions: 1119 examples, 0 failures
legacy_promotions: 792 examples, 0 failures
sample:   2 examples, 0 failures
i18n:     2 examples, 0 failures
core:     4435 examples, 11 failures (image/manipulative_query pre-existing)
api:      658 examples, 11 failures (image pre-existing)
backend:  766 examples, 6 failures (image pre-existing)
Total passing: 8390 examples across all suites
Total failures: 28 (all pre-existing ActiveStorage image adapter issues)
tokens used
586,937

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.
  • Recovered from all 4 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.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 37 minutes to install, slower than the median of the 10 comparable projects Argusic has measured.

Of the 11 ecommerce projects Argusic has installed and timed, solidus was the 10th fastest to reach a running state, and 9 of 11 reached one at all.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.20
Argusic Runner1/3Runs100.000.16

Topics (from GitHub)

ecommerceecommerce-frameworkecommerce-platformhacktoberfestrailsrubysolidusstorefront

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/solidus.svg)](https://argusic.com/subject/solidus)

Questions

Does solidus run?
Yes. solidus runs. Argusic installed and launched it on a clean machine in 37 minutes, hitting 4 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. 2 attempts are 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.20: 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?
37 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?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does solidus compare with the alternatives?
Of the 11 ecommerce projects Argusic has installed and timed, solidus was the 10th fastest to reach a running state, and 9 of 11 reached one at all.
Where is the evidence for solidus?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion