laravel-uptime-monitor
A powerful and easy to configure uptime and ssl monitor
Runssource: GitHubhomepagePHPMITcommit 04506831232f
PHP, MIT licensed. The project labels itself: laravel, monitoring, php, ssl and uptime monitor.
laravel-uptime-monitor runs. An Argusic agent installed it in 35 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Spatie laravel-uptime-monitor package is fully installed with 82 passing tests, using a custom PHP 8.3 environment built from Ubuntu packages with all required extensions.
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.
- PHP 8.3 not installed in container10 minutes
- ext-intl missing from PHP with pdo_sqlite - gnu-bulk PHP had intl but not pdo_sqlite, common had pdo_sqlite but not intl8 minutes
- Ubuntu PHP binary missing shared libraries (libxml2, libsodium, libargon2, libzip)6 minutes
- Test server boot sequence failed - php and composer commands not resolvable in PATH5 minutes
- pdo_sqlite.so had 'undefined symbol: php_pdo_unregister_driver' - ABI mismatch when loaded first3 minutes
- ext-zip not available and unzip command missing3 minutes
- Install time
- 35 minutes
- Cold machine to finish
- 36 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- Model tokens used
- 499,137
- Exact commit tested
- 04506831232f
- Container image
- sha256:4c3d41857be3
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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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.
/bin/sh -lc '# First error was PHP not found - took time to diagnose and fix with static PHP # Second error was missing intl in common build - fixed by switching to ubuntu PHP # Third error was pdo_sqlite ABI mismatch - fixed by loading pdo.so first # Fourth error was missing shared libs for ubuntu PHP - fixed by downloading lib packages # Fifth error was missing zip ext - fixed by downloading and installing zip + libzip # Sixth error was test server needing php/composer in PATH - fixed by creating wrappers # Total errors: 6 key issues echo "Summary done"' in /work/repo succeeded in 0ms: Summary done tokens used 499,137
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 35 minutes.
- 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/laravel-uptime-monitor)Questions
- Does laravel-uptime-monitor run?
- Yes. laravel-uptime-monitor runs. Argusic installed and launched it on a clean machine in 35 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test laravel-uptime-monitor?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 04506831232f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test laravel-uptime-monitor?
- The run that produced this verdict cost $0.29: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does laravel-uptime-monitor take to install?
- 35 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 laravel-uptime-monitor need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing laravel-uptime-monitor?
- 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.
- Where is the evidence for laravel-uptime-monitor?
- 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.