angie

Angie - drop-in replacement for nginx

Runssource: GitHubhomepageCBSD-2-Clausecommit b401553c1750

C, BSD-2-Clause licensed. The project labels itself: adc, apache, http, http3, https, load balancer, nginx and quic.

angie runs. An Argusic agent installed it in 17 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Angie 1.13.0 binary at /tmp/angie-install/sbin/angie serves HTTP on port 8080, returns 200 with correct body; test suite passes 4063 tests with 11 files failing due to environment constraints (no IPv6, no DNS, port conflicts) or pre-existing cert type detection issue.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.10 (measured)
recorded runs
2
last tested
stars
2,619
forks
113
open issues
47
watchers
47
size
37 MB
created
last push

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.

Time lost to each failure while testing angie, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • PCRE2 and zlib development headers not installed in container5 minutes
  • Perl module Test::Deep not installed2 minutes
  • Perl module JSON not installed, JSON-XS build fails due to missing Canary::Stability2 minutes
Install time
17 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
curl -s -o /dev/null -w %{http_code} http://localhost:8080/ returned 200; full test suite ran: 632 test files, 4063 tests passed, 421 skipped
Model tokens used
51,344
Exact commit tested
b401553c1750
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.

Let me compile the final report.
Here's a summary of what I did:
## Build & Install
Ran `./configure` with `--with-pcre=/tmp/pcre2-10.44 --with-zlib=/tmp/zlib-1.3.1 --with-http_ssl_mo…
## Errors Encountered
- **Missing PCRE2/zlib dev headers**: Not installed in container (no root). Fix: downloaded and bui…
- **Missing Perl modules `Test::Deep` and `JSON`**: Needed by the test harness. Fix: installed via …
- **11 test files failing**: All are environment-specific (no IPv6, no DNS resolver, port conflicts…
## Test Results
- **632 test files**, **4063 tests passed** (60 actual test failures across 11 files, all environme…
- 421 tests skipped (feature-dependent: HTTP/2, HTTP/3, ACME, mail, stream, etc.)
- Verified HTTP serving: `curl -s http://localhost:8080/` returned `200` with body `<html><body><h1…

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.
  • Installed in 17 minutes.
  • Recovered from all 3 errors 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 BSD-2-Clause, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.10
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

adcapachehttphttp3httpsload-balancernginxquicreverse-proxy

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/angie.svg)](https://argusic.com/subject/angie)

Questions

Does angie run?
Yes. angie runs. Argusic installed and launched it on a clean machine in 17 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test angie?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit b401553c1750. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test angie?
The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does angie take to install?
17 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 angie need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing angie?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for angie?
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.

Discussion