nesta

File Based CMS and Static Site Generator

Runssource: GitHubhomepageRubyMITcommit 8597b9a3854b

Ruby, MIT licensed. The project labels itself: cms, file based cms, haml, markdown, ruby, sass, sinatra and sinatra application.

nesta runs. An Argusic agent installed it in 28 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Ruby 3.2.3 installed locally from debs, bundler 4.0.6 installed, all 42 gem dependencies installed, all 203 tests pass with 0 failures, the Rack app starts and returns HTTP 200 for valid pages and articles.xml and HTTP 404 for unknown paths

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 96.7 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96.7 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
2
last tested
stars
899
forks
120
open issues
5
watchers
15
size
1 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 nesta, 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 (no root, no rvm/rbenv/conda)8 minutes
  • Shebangs in gem/bundle scripts pointed to /usr/bin/ruby3.2 which didn't exist5 minutes
  • Lockfile required bundler 4.0.6 but system had 2.4.193 minutes
  • rackup gem not bundled (not in Gemfile)2 minutes
Install time
28 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
All 203 test suite tests passed (0 failures, 0 errors, 210 assertions). App launched with rackup+WEBrick: curl returned HTTP 200 on /, 200 on /test-page, 200 on /articles.xml, 404 on /nonexistent
Model tokens used
273,515
Exact commit tested
8597b9a3854b
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

echo "done"' in /work/repo
 succeeded in 2974ms:
--- Final Verification ---
Homepage: 200
Test page: 200
Non-existent: 404
Atom feed: 200
done
All systems go. Let me compile the final result.
tokens used
273,515
All systems go. Let me compile the final result.

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 MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

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

Of the 30 cms projects Argusic has installed and timed, nesta was the 27th fastest to reach a running state, and 27 of 30 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.04
Argusic Runner1/3Runs93.330.16

Topics (from GitHub)

cmsfile-based-cmshamlmarkdownrubysasssinatrasinatra-applicationssgstatic-site-generatortextile

Embed the badge

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

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

Questions

Does nesta run?
Yes. nesta runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test nesta?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8597b9a3854b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test nesta?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does nesta 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 nesta need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing nesta?
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 nesta compare with the alternatives?
Of the 30 cms projects Argusic has installed and timed, nesta was the 27th fastest to reach a running state, and 27 of 30 reached one at all.
Where is the evidence for nesta?
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