hyde

HydePHP - Static Site Generator with the power of Laravel and the simplicity of Markdown.

Runssource: GitHubhomepagePHPMITcommit ede2acbc844e

PHP, MIT licensed. The project labels itself: blog engine, documentation generator, hyde, hydephp, laravel, php, static site generator and tailwind.

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

HydePHP 2.0.3 installed, CLI builds static sites producing valid HTML, the realtime compiler server responds HTTP 200, and the 6 project tests pass with 16 assertions and 0 errors.

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.06 (measured)
recorded runs
1
last tested
stars
494
forks
18
open issues
5
watchers
7
size
2 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 hyde, 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.

  • Missing test base classes (TestCase.php, UnitTestCase.php)4 minutes
  • No PHP binary found in container2 minutes
  • PHPUnit 12 incompatible with Laravel Zero 11 ErrorHandler::enable() signature2 minutes
  • Facade root not set in UnitTestCase resetKernel()2 minutes
  • Composer not available1 minute
  • Missing Mockery for Laravel console testing1 minute
Install time
12 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
php vendor/bin/phpunit passed 6 tests, 16 assertions, 0 errors; curl -s -o /dev/null -w '%{http_code}' http://localhost:8080 returned 200; php hyde build generates valid _site/index.html with proper <html></html> structure; php hyde --version displays 2.0.3
Model tokens used
573,987
Exact commit tested
ede2acbc844e
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.

# Final version output
php hyde --version 2>&1 | head -5" in /work/repo
 succeeded in 45ms:
1
1
app.css
     __ __        __    ___  __ _____
    / // /_ _____/ /__ / _ \/ // / _ \
   / _  / // / _  / -_) ___/ _  / ___/
  /_//_/\_, /\_,_/\__/_/  /_//_/_/
tokens used
573,987

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 6 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.

What did not, or is not known

  • Took 12 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 5 blog-engine projects Argusic has installed and timed, hyde was the 4th fastest to reach a running state, and 5 of 5 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 Runner1/3Runs100.000.06

Topics (from GitHub)

blog-enginedocumentation-generatorhydehydephplaravelphpstatic-site-generatortailwindtailwindcss

Embed the badge

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

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

Questions

Does hyde run?
Yes. hyde runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test hyde?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ede2acbc844e. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test hyde?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does hyde take to install?
12 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 hyde need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing hyde?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does hyde compare with the alternatives?
Of the 5 blog-engine projects Argusic has installed and timed, hyde was the 4th fastest to reach a running state, and 5 of 5 reached one at all.
Where is the evidence for hyde?
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.

Discussion