sulu
Core framework that implements the functionality of the Sulu content management system
Runssource: GitHubhomepagePHPMITcommit ed0dbfc273e4
PHP, MIT licensed. The project labels itself: admin, cmf, cms, hacktoberfest, php, sulu and symfony.
sulu runs. An Argusic agent installed it in 28 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Sulu CMS core framework builds and runs: PHP static binary 8.4.24, composer dependencies installed, MariaDB 10.11 stood up from portable binaries, all PHP test suites pass with zero failures on real MySQL backend, and 98.9% of JavaScript tests pass after minor jest-dom v6 compatibility patches.
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.
- MySQL database required for bundle tests using platform-specific SQL8 minutes
- bin/runtests spawns PHPUnit sub-process with default memory_limit=128M4 minutes
- PHP not found in container3 minutes
- rokka/imagine-vips requires ext-vips/ext-ffi not in static PHP2 minutes
- JS tests: @testing-library/jest-dom/extend-expect removed in v62 minutes
- JS tests: transformIgnorePatterns excluded local sulu-* bundles (ESM source)2 minutes
- Install time
- 28 minutes
- Cold machine to finish
- 59 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- PHP: php bin/runtests --all exit 0, 'Everything is AWESOME!', all 25 suites pass (component 690 tests, bundle suites total ~3000+ tests). MariaDB: mysql -h127.0.0.1 -u root -e 'SELECT VERSION()' returned 10.11.14. JS: npm test -> 447/452 suites pass, 3915/3925 tests pass.
- Model tokens used
- 2,813,993
- Exact commit tested
- ed0dbfc273e4
- 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.
2,813,993 Now I have all data. Let me compile the final result. **Summary of what was done and verified:** - Installed static PHP 8.4.24 with all extensions (no root required) - Installed Composer and removed the vips dev dependency (missing ext-vips, CI doesn't install it e… - Ran `composer install` successfully with all dependencies - `npm install` with 1575 packages succeeded - Set up MariaDB 10.11 from extracted `.deb` packages without root (listening on 127.0.0.1:3306) - Full PHP test suite against real MariaDB: **exit 0, "Everything is AWESOME!"** — all bundle suite… - Patched 9 JS test files for `@testing-library/jest-dom` v6 API change - Patched `transformIgnorePatterns` for local `sulu-*` bundle symlinks - JS test suite: 447/452 suites pass, 3915/3925 tests pass (remaining failures are pre-existing: 3 …
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 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
- 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sulu)Questions
- Does sulu run?
- Yes. sulu runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test sulu?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ed0dbfc273e4. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test sulu?
- The run that produced this verdict cost $0.56: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does sulu 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 sulu need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing sulu?
- 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.
- Where is the evidence for sulu?
- 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.