diskover-community

Diskover Community Edition - Open source file indexer, file search engine and data management and analytics powered by Elasticsearch

Runssource: GitHubhomepagePHPApache-2.0commit c2ba335880e9

PHP, Apache-2.0 licensed. The project labels itself: crawler, disk space, disk space analyzer, disk usage, duplicate files, duplicatefilefinder, elasticsearch and file indexing.

diskover-community runs. An Argusic agent installed it in 21 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Elasticsearch 7.13.1 cluster green on localhost:9200, Python 3.12 virtualenv with diskover scanner indexes files to ES, and PHP 8.2.32 built-in server serves the diskover-web UI authenticating with default credentials diskover/darkdata showing both indexed indices.

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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.27 (measured)
recorded runs
2
last tested
stars
1,833
forks
185
open issues
3
watchers
52
size
34 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 diskover-community, 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.

  • Elasticsearch daemon failed silently due to stale pid file from prior run8 minutes
  • Elasticsearch 7.13.1 default heap (3.7GB) exceeds container memory (773MB); process OOM-killed6 minutes
  • No PHP or Nginx packages available (no root access)3 minutes
  • PEP 668 externally-managed-environment blocks system-wide pip install2 minutes
  • Python scanner failed with 'unable to open database file' because DATABASE path defaults to /var/www/diskover-web/diskoverdb.sqlite3 which does not exist1 minute
Install time
21 minutes
Cold machine to finish
23 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
curl http://localhost:9200/_cluster/health returned status:green, 1 node; Python scanner indexed /work/repo (823 docs, 0 errors) into diskover-repo-test; PHP built-in server on port 808x responded with 200 on /login.php, /dashboard.php, /index.php after authenticating with diskover/darkdata; Indices page lists diskover-test and diskover-repo-test from ES
Model tokens used
242,647
Exact commit tested
c2ba335880e9
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

    <link rel="stylesheet" href="css/diskover.css" media="screen" />
    <link rel="stylesheet" href="css/dataTables.bootstrap.min.css" media="screen" />
Everything works end to end. Let me compile the final result.
exec
/bin/sh -lc "# Keep ES running, verify process
ps aux | grep '[e]lasticsearch' | grep java | head -1" in /work/repo
 succeeded in 0ms:
runner      6087  7.0  0.0 5894960 437624 ?      Ssl  10:30   0:39 /home/runner/work/elasticsearch-…
All verified. Here is the final result with the required JSON.
tokens used
242,647
All verified. Here is the final result with the required JSON.

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 Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 21 minutes to install, slower than the median of the 25 comparable projects Argusic has measured.

Of the 26 crawler projects Argusic has installed and timed, diskover-community was the 22nd fastest to reach a running state, and 22 of 26 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.27
Argusic Runner1/3Runs with mocks92.000.20

Topics (from GitHub)

crawlerdisk-spacedisk-space-analyzerdisk-usageduplicate-filesduplicatefilefinderelasticsearchfile-indexingfile-managerfile-taggingfilesystemfilesystem-analysisfilesystem-indexerfilesystem-visualizationmetadataphppythonstoragestorage-analyticsweb-application

Embed the badge

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

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

Questions

Does diskover-community run?
Yes. diskover-community runs. Argusic installed and launched it on a clean machine in 21 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test diskover-community?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit c2ba335880e9. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test diskover-community?
The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does diskover-community take to install?
21 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 diskover-community need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing diskover-community?
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 diskover-community compare with the alternatives?
Of the 26 crawler projects Argusic has installed and timed, diskover-community was the 22nd fastest to reach a running state, and 22 of 26 reached one at all.
Where is the evidence for diskover-community?
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