Weave Code
Laravel Appkeep Laravel Package
appkeep/laravel-appkeep
appkeep/laravel-appkeep helps you keep your Laravel application healthy and running smoothly. It offers lightweight tools for monitoring, maintenance, and routine upkeep, with easy configuration that fits cleanly into your existing workflow and keeps your project reliably on track.
AppKeep (appkeep/laravel-appkeep) is a Laravel package for keeping your application healthy and well-maintained. It bundles routine health checks and housekeeping into one configurable toolkit, so you can catch problems early and automate the boring upkeep instead of wiring together one-off commands.
- Health checks for database, cache, queue, and storage drivers
- Scheduled maintenance such as log pruning and cache clearing
- Configurable alerts via mail, Slack, or custom channels
- Artisan commands for on-demand checks and manual runs
- Sensible defaults with publishable configuration
Frequently asked questions about Laravel Appkeep
- How do I install appkeep/laravel-appkeep in a Laravel application?
- Install it as a Composer package and let Laravel package discovery register the service provider, following the repository instructions. The overview describes AppKeep as a private beta, so access may be gated and you should confirm availability before adding it to composer.json. During evaluation, pin an exact version such as 0.6.2 instead of using a floating ^0.6 constraint.
- Is appkeep/laravel-appkeep a runtime dependency or a require-dev package?
- The provided technical assessment flags this as the most important unknown for architectural fit. The monitoring overview implies runtime-facing health and status endpoints, but the SpecContext component may be a dev/test helper, and the assessment could not confirm whether the package registers middleware or hooks into the request lifecycle. Start it as require-dev in a spike branch and confirm service-provider side effects before treating it as a production dependency.
- Which Laravel and PHP versions are supported by laravel-appkeep?
- The context does not provide a confirmed Laravel or PHP support matrix. The 0.6.2 bugfix for SpecContext on PHP 7.4 suggests that PHP 7.4 is still in the support or test matrix, even though it has been end-of-life since November 2022. Validate Laravel 9, 10, 11, and 12 plus PHP 8.2 and 8.3 explicitly in CI before adoption rather than assuming modern-version coverage.
- What does SpecContext do in appkeep/laravel-appkeep?
- SpecContext appears to be a specification, assertion, or context-capture utility that inspects memory size, according to the technical assessment. The assessment considers it most plausibly a dev/test-time helper, but whether it also registers runtime middleware remains unconfirmed. Version 0.6.2 fixed SpecContext failing to resolve memory size on PHP 7.4, so test memory_limit edge cases and confirm whether failures are loud or silent.
- Can AppKeep monitor Laravel applications without SSH access?
- Yes, the overview explicitly states that AppKeep works without SSH access. It is described as a complete Laravel monitoring toolkit for uptime, application health, queues, scheduled commands, and more. That makes it relevant for teams that cannot or do not want to rely on server-level access for monitoring.
- How does AppKeep monitor queues and scheduled commands in Laravel?
- The package overview says AppKeep provides configurable checks for queues and scheduled commands as part of its Laravel monitoring toolkit. It also mentions status endpoints and alerts to help catch issues early. Exact configuration details are not included in the provided context, so consult the repository and private-beta documentation for the check definitions and alert setup.
- Is appkeep/laravel-appkeep production-ready?
- At v0.6.x the package is pre-1.0, so API stability guarantees are weak. The assessment recommends treating it as a dev dependency until a 1.0 release or explicit maintainer confirmation of stability and support matrix. It also notes single-organization maintenance, sparse changelog detail, and unverified Laravel/PHP support, so production use requires staging validation and exact version pinning.
- What are the main risks of adopting laravel-appkeep before 1.0?
- Pre-1.0 semver permits breaking changes in minor releases, so every 0.x bump should be treated as potentially breaking. The assessment highlights environment-detection regressions such as the PHP 7.4 memory-size bug fixed in 0.6.2, plus unknown runtime coupling, a single-maintainer bus factor, and unverified Laravel/PHP coverage. Mitigate by pinning versions, reading changelogs, and running the package in CI against your actual matrix.
- How should I evaluate appkeep/laravel-appkeep in a Laravel project?
- Use a spike branch, add the package as require-dev, and pin exactly 0.6.2 until API stability is understood. Exercise SpecContext on your target PHP version, including memory_limit edge cases such as -1, 0, and suffixed values, and confirm there are no production service-provider side effects like config publishing, middleware, or migrations. If it proves useful in CI, document internal conventions before considering a runtime dependency.
- What alternatives should I compare with appkeep/laravel-appkeep?
- The provided context does not name specific alternatives, so avoid assuming a direct drop-in replacement. Evaluate AppKeep against your existing Laravel health endpoint, uptime monitoring, queue monitoring, and scheduler monitoring tooling. The key comparison points are whether it runs at runtime or only in CI, its Laravel/PHP support matrix, and its pre-1.0 maintenance risk.
Weaver
How can I help you explore Laravel packages today?