blackcandy
A self hosted music streaming server
Runssource: GitHubRubyMITcommit 6c36030c60c6
Ruby, MIT licensed. The project labels itself: audio, hotwire, music, music player, music streaming, musicplayer, rails and ruby.
blackcandy runs. An Argusic agent installed it in 30 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Ruby 4.0.7, Node.js 20.11.0 installed; all 39 Gemfile dependencies and 152 gems installed; all 416 tests pass with 1049 assertions and 0 failures; Rails dev server boots on port 3000 responding with 200 on /up and 302 on login POST; SQLite development and test databases seeded with admin user [email protected]/foobar.
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.
- Ruby 4.0.7 not installed in container (missing Ruby entirely)10 minutes
- libvips.so.42 not found at runtime (missing library and all transitive dependencies)7 minutes
- One test failed due to missing libvips dependencies — MediaSyncAllJobTest#test_should_change_syncing_status5 minutes
- pg gem (optional PostgreSQL driver) failed to compile due to missing libpq-dev3 minutes
- Node.js was v18.19.1 but project requires ^20.17.0 (specified 20.11.0 in .node-version)2 minutes
- Install time
- 30 minutes
- Cold machine to finish
- 42 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- rails test:all exited 0 with 416 runs, 1049 assertions, 0 failures, 0 errors; rails server booted and /up returned 200 with green background body; POST /sessions returned 302 redirect
- Model tokens used
- 257,828
- Exact commit tested
- 6c36030c60c6
- 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.
echo "---" echo "Test results: 416 runs, 1049 assertions, 0 failures, 0 errors" echo "Server: booted successfully, POST /sessions returned 302 redirect" echo "Health endpoint: curl /up returned HTTP 200 with green background"' in /work/repo succeeded in 0ms: /bin/sh: 2: lsof: not found ruby 4.0.7 (2026-09-15 revision 229531a6cf) +PRISM [x86_64-linux] Test results: 416 runs, 1049 assertions, 0 failures, 0 errors Server: booted successfully, POST /sessions returned 302 redirect Health endpoint: curl /up returned HTTP 200 with green background tokens used 257,828
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 5 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 30 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
Of the 5 audio projects Argusic has installed and timed, blackcandy was the 5th fastest to reach a running state, and 4 of 5 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)
audiohotwiremusicmusic-playermusic-streamingmusicplayerrailsrubyself-hosted
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/blackcandy)Questions
- Does blackcandy run?
- Yes. blackcandy runs. Argusic installed and launched it on a clean machine in 30 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test blackcandy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6c36030c60c6. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test blackcandy?
- The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does blackcandy take to install?
- 30 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 blackcandy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing blackcandy?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does blackcandy compare with the alternatives?
- Of the 5 audio projects Argusic has installed and timed, blackcandy was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for blackcandy?
- 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.