luya

LUYA is a scalable web framework and content management system with the goal to please developers, clients and users alike.

Runssource: GitHubhomepagePHPMITcommit 7960f23c7153

PHP, MIT licensed. The project labels itself: admin, angular, bootstrap4, cms, hacktoberfest, javascript, luya and php.

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

LUYA installs and boots under static PHP 8.3 with a local MariaDB (127.0.0.1:8888); the PHPUnit suite executes 331 tests with only the intl/ICU-dependent Formatter assertion failing (plus 1 pre-existing risky output-buffer test), the remaining 330 tests pass, and the LUYA console CLI lists and runs its core commands.

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

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.44 (measured)
recorded runs
2
last tested
stars
801
forks
200
open issues
4
watchers
70
size
83 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 luya, 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.

  • MySQL/MariaDB absent; tests need mysql at 127.0.0.1:88888 minutes
  • Access denied for 'root'@'localhost' (using password: YES): Yii PDO connected via localhost host while grants were for 127.0.0.14 minutes
  • PHP binary missing in container (no root to apt-install)3 minutes
  • HealthControllerTest fails with 'public_html/storage: directory exists already' after any prior health run (test asserts fresh-dir state)3 minutes
  • FormatterTest::testDefaultSettingsFromGivenArray fails: expected 2017/2017/2017 got 2017201720172017/2017201720172017/20172017201720173 minutes
Install time
21 minutes
Cold machine to finish
22 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
composer install succeeded (76 packages); fresh-tree `php vendor/bin/phpunit` exited 1 with: Tests: 331, Assertions: 874, Failures: 1 (Formatter/intl), Risky: 1, Errors: 0; MariaDB served 39 test tables on 127.0.0.1:8888; `php core/bin/luya` printed the full command list; `php core/bin/luya health/index` ran against core and reported the expected missing kickstarter files
Model tokens used
2,046,827
Exact commit tested
7960f23c7153
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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.

- DB-auth and health-state issues diagnosed and fixed; `HealthControllerTest` passes in a clean tre…
- `core/bin/luya` CLI answers with full command list; `migrate/history` runs against the DB.
- Unfixable gap: `FormatterTest::testDefaultSettingsFromGivenArray` needs PHP intl with an old ICU;…
tokens used
2,046,827
All core verifications are done. Final state:
- `composer install` succeeded (76 packages).
- MariaDB 10.11.7 stood up locally at `127.0.0.1:8888`, schema `1.0.0.sql` loaded (39 tables).
- Fresh full suite: `Tests: 331, Assertions: 874, Failures: 1 (Formatter/intl), Risky: 1`, no error…
- DB-auth and health-state issues diagnosed and fixed; `HealthControllerTest` passes in a clean tre…
- `core/bin/luya` CLI answers with full command list; `migrate/history` runs against the DB.
- Unfixable gap: `FormatterTest::testDefaultSettingsFromGivenArray` needs PHP intl with an old ICU;…

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 5 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 21 minutes to install, slower than the median of the 9 comparable projects Argusic has measured.

Of the 10 admin projects Argusic has installed and timed, luya was the 8th fastest to reach a running state, and 8 of 10 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/3Runs with mocks92.000.05
Argusic Runner1/3Runs100.000.44

Topics (from GitHub)

adminangularbootstrap4cmshacktoberfestjavascriptluyaphprest-apiyii2

Embed the badge

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

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

Questions

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