Laravel deployment self-test
Every panel below was measured while this page was being served — nothing here is cached and nothing is hard-coded. Reload and the numbers move.
Running PHP 8.5.10 with Laravel 12.69.1. This project declares php ^8.2, so 8.2, 8.3 and 8.4 are all valid choices in the deployment settings — whichever you picked is the number above.
All of pdo_mysql, mbstring, openssl, tokenizer, xml, ctype, json, curl are loaded.
Connected to "app_laravel_test1" over mysql. The server reports 10.5.29-MariaDB. The platform created this database, generated the password on the server and wrote it into .env — nothing was typed in by hand, and the platform itself never saw the password.
4 migration(s) have run, including this project's own deployment_checks table, which holds 2 row(s). One of those rows was written by the migration itself, so a deployment that skipped migrations could not show this.
This page has been served 322 time(s). The counter is a real UPDATE on every request, so a read-only or misconfigured connection shows as a failure rather than as a stale number.
Driver "database". A value was written and read back during this request. On the default database driver this exercises the sessions table too.
Store "database". A value was written and read back.
storage/app is writable by the web server. This is the check that fails when a hardened deployment forgets to leave storage/ writable, and it takes every session, log and cached view down with it.
Vite built 2 entrypoint(s) into public/build. The styling on this page is Tailwind compiled during the deployment — if this looks like a designed page rather than a wall of unstyled text, the build genuinely ran on the server.
Last ran at 2026-09-15 18:58:03. The platform installed the every-minute cron entry that Laravel's scheduler needs; without it every ->daily() and ->hourly() in an application silently never fires.