mm-wiki
MM-Wiki 一个轻量级的企业知识分享与团队协同软件,可用于快速构建企业 Wiki 和团队知识分享平台。部署方便,使用简单,帮助团队构建一个信息共享、文档管理的协作环境。
Runs with mockssource: GitHubGoMITcommit d976d0c60484
Go, MIT licensed. The project labels itself: api docs, confluence, docs, document management, documentation, documents, documentserver and dokuwiki.
mm-wiki runs, with stand-ins for the services it depends on. An Argusic agent installed it in 8 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
MM-Wiki v0.2.2 builds and runs on Go 1.21.13 with a Python mock MySQL server (port 3308). The application serves HTTP on port 8081, authenticates with admin:123456, and returns the main dashboard at HTTP 200 with the MM-Wiki interface.
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.
- MySQL/MariaDB not available - no root access to install system packages15 minutes
- Mock MySQL did not support COM_STMT_PREPARE (prepared statements) initially10 minutes
- COM_STMT_EXECUTE parameter value parsing was incorrect (wrong byte offsets, types/values interleaved, string encoding)8 minutes
- Login failed with binary protocol results since text row format was used after COM_STMT_EXECUTE5 minutes
- Go compiler not pre-installed - downloaded Go 1.21.13 tarball2 minutes
- mw_log table schema was missing path, post, get, referer, message, user_agent columns in mock2 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 34 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- curl -X POST -d 'username=admin&password=123456' localhost:8081/author/login returned {"code":1,"message":"登录成功!"} with session cookies; curl -L -b cookies localhost:8081/ returned HTTP 200 with <title>MM-Wiki</title>
- Model tokens used
- 571,370
- Exact commit tested
- d976d0c60484
- 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.
'"' 2>&1 | grep -E \""'^---|''^login_json|''^main_http"' in /work/repo
succeeded in 11902ms:
---TEST_SUMMARY---
login_json: {
main_http: 200
---END_SUMMARY---
The verification is solid. Let me now write the final result.
**ARGUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 8, "erro…
tokens used
571,370
The verification is solid. Let me now write the final result.
**ARGUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 8, "erro…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 8 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.
- Measured 2 times, so the result is not a one-off.
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.
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 | 2/3 | Runs with mocks | 92.00 | 0.68 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.48 |
Topics (from GitHub)
api-docsconfluencedocsdocument-managementdocumentationdocumentsdocumentserverdokuwikiwiki
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mm-wiki)Questions
- Does mm-wiki run?
- mm-wiki runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 8 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test mm-wiki?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d976d0c60484. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test mm-wiki?
- The run that produced this verdict cost $0.68: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mm-wiki take to install?
- 8 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 mm-wiki need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mm-wiki?
- 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 mm-wiki?
- 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.