WordOps
Install and manage a high performance WordPress stack with a few keystrokes
Runs with mockssource: GitHubhomepagePythonMITcommit 13a03e43df49
Python, MIT licensed. The project labels itself: automation, cache, cli, debian, lemp, mariadb, nginx and performance.
WordOps runs, with stand-ins for the services it depends on. An Argusic agent installed it in 23 minutes and hit 6 errors on a clean machine with no GPU, and the whole session was recorded.
WordOps 3.23.1 Python package installs and CLI framework loads in a venv. All subcommands (stack, clean, info, secure) parse arguments and respond. 10 of 19 tests pass without root. The 9 failing tests require root privileges and installed system packages (nginx, MySQL, PHP).
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 88.7 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.
- ModuleNotFoundError: No module named 'apt' (python3-apt system package not available)5 minutes
- ModuleNotFoundError: No module named 'imp' (nose incompatibility with Python 3.12)3 minutes
- ModuleNotFoundError: No module named 'pkg_resources'2 minutes
- PermissionError: copy2 ~/.gitconfig -> /root/.gitconfig1 minute
- PermissionError reading /proc/1/environ in grepcheck1 minute
- 9 tests failed: require root/system packages (nginx, mysql) for integration testing
- Install time
- 23 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 6 hit, 5 fixed with no human help
- How the result was proved
- pytest ran 19 tests: 10 passed (clean, info, secure_auth), 9 failed (root-requiring integration tests)
- Model tokens used
- 158,480
- Exact commit tested
- 13a03e43df49
- 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.
**Errors found and fixed:** 1. **`ModuleNotFoundError: No module named 'imp'`** - The `nose` package (installed as a dependency… 2. **`ModuleNotFoundError: No module named 'pkg_resources'`** - The `wo/__init__.py` uses `pkg_reso… 3. **`PermissionError: /root/.gitconfig`** - `wo/core/variables.py` tries to copy git config to `/r… 4. **`ModuleNotFoundError: No module named 'apt'`** - The `python3-apt` system package was missing.… 5. **`Unable to search string container=lxc in /proc/1/environ`** - `wo/core/fileutils.py` hit a Pe… The remaining 9 failing tests all require either root privileges to write to `/etc/` or actual ngin… Let me compile the final results: - **install_succeeded**: true - `pip install -e ".[testing]"` succeeded in the venv - **launch_succeeded**: true - test suite executed and returned results (10 passed, 9 failed) - **test_depth**: "tier2_mock" - I created stubs for missing system packages (nose, apt) and create… - **verified_how**: "pytest ran 19 tests: 10 passed, 9 failed (integration tests requiring root/sys…
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
- 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.
- Took 23 minutes to install, slower than the median of the 10 comparable projects Argusic has measured.
- Hit 6 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 11 automation projects Argusic has installed and timed, WordOps was the 10th fastest to reach a running state, and 7 of 11 reached one at all.
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 | 88.67 | 0.32 |
Topics (from GitHub)
automationcacheclidebianlempmariadbnginxperformancephpredisreverse-proxyserver-managementsslubuntuwordopswordpresswordpress-site
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/wordops)Questions
- Does WordOps run?
- WordOps runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 23 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test WordOps?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 13a03e43df49. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test WordOps?
- The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does WordOps take to install?
- 23 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 WordOps need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing WordOps?
- 6 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 WordOps compare with the alternatives?
- Of the 11 automation projects Argusic has installed and timed, WordOps was the 10th fastest to reach a running state, and 7 of 11 reached one at all.
- Where is the evidence for WordOps?
- 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.