Diagnostics
Diagnostics gives Capell operators one place to check system health, queues, config drift, permissions, and package install status.
What Diagnostics helps you do
This private package is outside the Released and Beta channels, so no public install path is available.
Workflow screenshots
6 capturesDiagnostics gives Capell operators one place to check system health, queues, config drift, permissions, and package install status.
A guarded command palette runs trusted capell:* operations without scattering ad hoc debug pages around the app.
Teams find setup and package problems before they become visitor-facing failures.
Use it when a Capell site needs clearer production readiness and support signals.
Review the documentation and screenshots on this page before enabling it on a production Capell site.
What changes on your site
Review the admin, public, data, scheduled, and command surfaces Diagnostics adds when enabled.
- Developer Tools
- Diagnostics
- Operations
Install after you have checked the fit.
Confirm version compatibility, support, data access, migrations, retained data, and removal steps first. Then install the Composer package from the account that owns access.
-
01
Require the package
composer require capell-app/diagnostics -
02
Register the extension
php artisan capell:extension:enable diagnostics -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Diagnostics
Switch the evaluation lens to see how different roles should assess this package before installing it.
One screen confirms the site is healthy — what to verify
Keep the homepage responding while deliberately failing a queue worker and migration check. The gated diagnostics view should reveal that the site is unhealthy despite the successful front-page request.
Read more Show less
Expected evidence: The screen brings queued and failed jobs, migration state, configuration drift and frontend build status together. A successful homepage is no longer the only health signal.
Choose a lighter option when: Acting on what it shows still needs a technical hand on their side. External uptime monitoring watches a different, outside-in angle, so site owners would treat the two as complementary rather than swap one for the other.
Release and download evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
0 releasesNo package release history is published yet. Check the source and documentation before installing.
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy hosts paid marketplace checkout and issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the licence, receipt, support history, and future install access. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.
No approved reviews yet. Reviews from eligible customers appear here after moderation.
