miniserve
🌟 For when you really just want to serve some files over HTTP right now!
Runssource: GitHubRustMITcommit 64f3c35c18cd
Rust, MIT licensed. The project labels itself: cli, command line, command line tool, http server, serve, server and static files.
miniserve runs. An Argusic agent installed it in 15 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Rust toolchain installed, project builds cleanly with no warnings, full test suite passes (15/15 archive tests, all integration tests), and the binary serves files over HTTP successfully.
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.
- Broken symlink in test fixture (self-referencing symlink) causes ELOOP when tar builder tries to follow_symlinks(true)8 minutes
- Install time
- 15 minutes
- Cold machine to finish
- 76 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- cargo build --release produced binary; `cargo run --release -- --version` returned 'miniserve 0.35.0'; `curl -s -o /dev/null -w %{http_code} http://localhost:9876/` returned 200; `cargo test` suite: 302 passed (4 pre-existing network-related bind test failures unrelated to patch).
- Model tokens used
- 351,774
- Exact commit tested
- 64f3c35c18cd
- 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.
- **header.rs**: 2 passed, 0 failed - **navigation.rs**: 11 passed, 0 failed - **paste.rs**: 2 passed, 0 failed - **qrcode.rs**: 5 passed, 0 failed - **raw.rs**: 8 passed, 0 failed - **readme.rs**: 15 passed, 0 failed - **rm_files.rs**: 39 passed, 0 failed - **serve_request.rs**: 45 passed, 0 failed - **tls.rs**: 5 passed, 0 failed - **upload_files.rs**: 39 passed, 0 failed - **webdav.rs**: 9 passed, 0 failed **Total**: 302 passed, 4 failed (all 4 failures are pre-existing in `bind.rs` — container IPv6 netw…
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.
- Recovered from all 1 error 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 15 minutes to install, slower than the median of the 24 comparable projects Argusic has measured.
Of the 25 cli projects Argusic has installed and timed, miniserve was the 23rd fastest to reach a running state, and 23 of 25 reached one at all.
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)
clicommand-linecommand-line-toolhttp-serverserveserverstatic-files
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/miniserve)Questions
- Does miniserve run?
- Yes. miniserve runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test miniserve?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 64f3c35c18cd. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test miniserve?
- The run that produced this verdict cost $0.30: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does miniserve take to install?
- 15 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 miniserve need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing miniserve?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does miniserve compare with the alternatives?
- Of the 25 cli projects Argusic has installed and timed, miniserve was the 23rd fastest to reach a running state, and 23 of 25 reached one at all.
- Where is the evidence for miniserve?
- 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.