movary
A self-hosted web app for tracking, rating, and exploring your movie watch history.
Runssource: GitHubPHPMITcommit 9953a06fae56
PHP, MIT licensed. The project labels itself: emby, jellyfin, letterboxd, movie, netflix, plex, self hosted and tmdb.
movary runs. An Argusic agent installed it in 3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Movary 144 unit tests pass, all static analysis checks pass, PHP built-in web server serves /login (200), /docs/api (200), and unauthenticated redirects (302), SQLite database with 24 tables created via all 36 migrations.
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.
- Install time
- 3 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- phpunit -c settings/phpunit.xml --testsuite unit: 144 tests passed, 313 assertions; phpcs: 0 errors; phpstan: OK; psalm: 0 errors; php -S built-in server on port 8081: GET /login returned 200, GET /docs/api returned 200, GET /jobs returned 302 (expected redirect)
- Model tokens used
- 292,643
- Exact commit tested
- 9953a06fae56
- 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.
292,643 All 24 tables created successfully. Everything is working. Let me compile the final result. Here's the complete rundown: **Install:** Downloaded a static PHP 8.5.8 CLI binary (since no PHP was installed), installed Compo… **Verification results:** - `php bin/console.php` — console app boots, lists all commands - `php vendor/bin/phpunit -c settings/phpunit.xml --testsuite unit` — **144 tests, 313 assertions, … - `php vendor/bin/phpcs --standard=./settings/phpcs.xml` — **no CS errors** - `php vendor/bin/phpstan analyse ...` — **OK, no errors** - `php vendor/bin/psalm ...` — **no errors found** (1100 info-level issues, 94.18% type inference) - `php -S 127.0.0.1:8081 -t public/` — web server runs, `/login` returns 200, `/docs/api` returns 2… **Errors:** None encountered. The environment was missing PHP, Composer, and Docker — all solved wi…
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 3 minutes, faster than the median of the 3 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- 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.
Of the 4 emby projects Argusic has installed and timed, movary was the 1st fastest to reach a running state, and 3 of 4 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 3 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
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)
embyjellyfinletterboxdmovienetflixplexself-hostedtmdbtrakt-tv
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/movary)Questions
- Does movary run?
- Yes. movary runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test movary?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9953a06fae56. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test movary?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does movary take to install?
- 3 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 movary need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing movary?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does movary compare with the alternatives?
- Of the 4 emby projects Argusic has installed and timed, movary was the 1st fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for movary?
- 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.