DoraCMS
DoraCMS 是一个基于 EggJS 3.x + Vue 3 + TypeScript 的现代化内容管理系统，采用 pnpm monorepo 架构管理。它不仅仅是一个 CMS 系统，更是一个优秀的企业级应用架构实践。
Runs with mockssource: GitHubhomepageJavaScriptMITcommit bdaded858ce6
JavaScript, MIT licensed. The project labels itself: cms, doracms, eggjs, element ui, mit license, mongodb, nodejs and nodejscms.
DoraCMS runs, with stand-ins for the services it depends on. An Argusic agent installed it in 25 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies install and two standalone test suites pass (68 total). The EggJS app initializes with in-memory MongoDB but integration tests are blocked by Node 18 incompatibility with egg-watcher/EventSource and egg-mock context mocking.
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.
- globalThis.File not defined in Node 18 causing undici@7 to crash5 minutes
- MongoDB not available for integration tests5 minutes
- EventSource is not a constructor in egg-watcher on Node 184 minutes
- env.js getEnv returns default even when env var is explicitly empty string (REDIS_HOST=)3 minutes
- pnpm install blocked build scripts for 10 packages2 minutes
- pnpm not found in container1 minute
- Install time
- 25 minutes
- Cold machine to finish
- 50 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- npx mocha --require stubs/setup-mocha.js test/app/repository/utils/EnhancedDataTransformer.phase3.test.js (36 passed) && npx mocha --require stubs/setup-mocha.js test/utils/webhookSignature.test.js (32 passed). egg-bin test with in-memory MongoDB boots app but integration tests fail with Node 18 compatibility errors.
- Model tokens used
- 488,111
- Exact commit tested
- bdaded858ce6
- 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.
process.exit(failures ? 1 : 0); }); TESTRUNNER echo \"created\"" in /work/repo succeeded in 0ms: created Now let me produce the final comprehensive result. The standalone tests (EnhancedDataTransformer.phase3.test.js and webhookSignature.test.js) pass wit… tokens used 488,111 Now let me produce the final comprehensive result. The standalone tests (EnhancedDataTransformer.phase3.test.js and webhookSignature.test.js) pass wit…
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
- Recovered from all 7 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.
- Took 25 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 8 cms projects Argusic has installed and timed, DoraCMS was the 6th fastest to reach a running state, and 7 of 8 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 | 92.00 | 0.26 |
Topics (from GitHub)
cmsdoracmseggjselement-uimit-licensemongodbnodejsnodejscmspnpmqiankuntypescriptvuevuejs
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/doracms)Questions
- Does DoraCMS run?
- DoraCMS runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 25 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test DoraCMS?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bdaded858ce6. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test DoraCMS?
- The run that produced this verdict cost $0.26: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does DoraCMS take to install?
- 25 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 DoraCMS need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing DoraCMS?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does DoraCMS compare with the alternatives?
- Of the 8 cms projects Argusic has installed and timed, DoraCMS was the 6th fastest to reach a running state, and 7 of 8 reached one at all.
- Where is the evidence for DoraCMS?
- 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.