BookStack
NOW MANAGED ON CODEBERG
Runs with mockssource: GitHubhomepagePHPMITcommit 1633b3ab281b
PHP, MIT licensed. The project labels itself: bookstack, documentation, laravel, php, selfhosted and wiki.
BookStack runs, with stand-ins for the services it depends on. An Argusic agent installed it in 31 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
BookStack PHP dependencies installed, MariaDB 10.11.6 serving on port 3307, all 110+ migrations applied successfully, 1561 of 1622 tests pass or are non-critical failures (LDAP, PDF export, config defaults), the Laravel artisan CLI and development HTTP server both start and respond.
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 92 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.
- No MySQL database server available3 minutes
- PHP and Composer not installed2 minutes
- Migration macro 'indexed()' undefined in Laravel 121 minute
- LDAP tests fail (7 errors, 22 failures) - PHP ext-ldap not loaded1 minute
- PDF export test failure - php not in PATH for subprocess1 minute
- Config tests fail - STORAGE_TYPE=local_secure not supported and MySQL port mismatch 3307 vs 33061 minute
- Install time
- 31 minutes
- Cold machine to finish
- 33 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- phpunit exited with 7 errors, 26 failures, 4 skipped, 29 risky across 1622 tests with 7914 assertions
- Model tokens used
- 895,582
- Exact commit tested
- 1633b3ab281b
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Failures: 26 (22 LDAP + 1 PDF export + 2 config tests with local_secure + 1 port 3307 vs 3306) Skipped: 4 Risky: 29 exec /bin/sh -lc 'cd /work/repo && /tmp/php -d memory_limit=1024M vendor/bin/phpunit --configuration php… succeeded in 147400ms: ERRORS! Tests: 1622, Assertions: 7914, Errors: 7, Failures: 26, Skipped: 4, Risky: 29. Here's the final summary of my work: tokens used 895,582 Here's the final summary of my work:
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
- Installed in 31 minutes.
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.24 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/bookstack)Questions
- Does BookStack run?
- BookStack runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 31 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test BookStack?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1633b3ab281b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test BookStack?
- The run that produced this verdict cost $0.24: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does BookStack take to install?
- 31 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 BookStack need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing BookStack?
- 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 BookStack?
- 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.