fussel

Static photo gallery generator with EXIF info, face tag overlays, watermarking and Docker support

Runssource: GitHubPythonMITcommit 08cc8128196e

Python, MIT licensed. The project labels itself: docker, exif, face detection, gallery, photo gallery, photos, python and self hosted.

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

Fussel is fully installed and operational: gallery generation, React frontend build, and HTTP serving all work end-to-end; all 139 tests across Python (112) and JavaScript (27) suites pass.

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.11 (measured)
recorded runs
1
last tested
stars
314
forks
26
open issues
5
watchers
3
size
5 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 fussel, 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.

  • Node.js v18 incompatible with react-router-dom (needs >=20.0.0) and vite (needs >=22.12.0)2 minutes
  • test_main_success FileNotFoundError writing .nojekyll to /test/output2 minutes
  • JS test files 3/6 failed due to missing _gallery stub data files for vitest import resolution2 minutes
  • uv not found in PATH1 minute
  • yarn not found in PATH1 minute
  • test_supported_extensions assertion failed (expected old extension list without .avif)1 minute
Install time
10 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
pytest passed 112/112; vitest passed 27/27; `python -m fussel.fussel` generated gallery from a real photo inside an album directory; `curl -s -o /dev/null -w %{http_code} http://localhost:8000/` returned 200; Pillow verified output image dimensions
Model tokens used
91,810
Exact commit tested
08cc8128196e
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.

- `yarn` not in PATH → `npm install -g yarn` with `~/.npm-global` prefix
- Node.js v18 incompatible with `react-router-dom` (needs ≥20) and `vite` (needs ≥22.12) → download…
**Fixes applied** (3 code changes):
- `tests/test_config.py` — updated `test_supported_extensions` assertion to include `.avif` (the co…
- `tests/test_fussel.py` — fixed `test_main_success` mock to create the output directory before wri…
- Created `fussel/web/src/_gallery/site_data.js`, `albums_data.js`, `people_data.js`, `photos_data.…
**Verification results** (all passed):
- Python test suite: **112/112 passed**
- JS test suite: **27/27 passed** across 6 test files
- End-to-end gallery generation: created a real test JPEG, configured the app, ran `python -m fusse…
- Serving: `curl http://localhost:8000/` returned **HTTP 200**
- Image output: Pillow confirmed generated thumbnails are valid 100×100 RGB JPEGs

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 6 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 MIT, as reported by its host.

What did not, or is not known

  • Took 10 minutes to install, slower than the median of the 23 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 24 docker projects Argusic has installed and timed, fussel was the 14th fastest to reach a running state, and 17 of 24 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.
  • A quick evaluation: it was running 10 minutes after the clone.

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 Runner1/3Runs100.000.11

Topics (from GitHub)

dockerexifface-detectiongalleryphoto-galleryphotospythonself-hostedstatic-sitestatic-site-generator

Embed the badge

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

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

Questions

Does fussel run?
Yes. fussel runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test fussel?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 08cc8128196e. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test fussel?
The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does fussel take to install?
10 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 fussel need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing fussel?
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.
How does fussel compare with the alternatives?
Of the 24 docker projects Argusic has installed and timed, fussel was the 14th fastest to reach a running state, and 17 of 24 reached one at all.
Where is the evidence for fussel?
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.

Discussion