Weave Code
Tomato User Activities Laravel Package
tomatophp/tomato-user-activities
Laravel package for tracking and displaying user activities in TomatoPHP admin panels. Logs logins, CRUD events, and custom actions, with a ready-made Filament resource for browsing activity history and auditing user behavior.
Tomato User Activities is a lightweight activity-logging extension for TomatoPHP that records what users do across your Laravel application. It captures events such as logins, logouts, profile updates, and CRUD actions, storing each entry with the associated user, timestamp, and request context—so you can audit changes and debug issues from one place.
- Automatic tracking of authentication and model events
- Per-user activity timeline with timestamps and IP/user-agent context
- Configurable logging and retention settings
- Ready-to-use Filament resources for browsing and filtering logs
- Seamless integration with the TomatoPHP admin panel
Frequently asked questions about Tomato User Activities
- How do I install tomatophp/tomato-user-activities in a Laravel app?
- Install it with Composer, then register the service provider if your Laravel version does not auto-discover it. The package is expected to publish config and migration files, so review and run those in a non-production environment first. Validate the published schema and configuration before instrumenting real user actions.
- Which Laravel and PHP versions does tomato-user-activities support?
- The provided evaluation does not list explicit Laravel or PHP version constraints, so check the package composer.json and test matrix before adoption. Confirm your database engine, queue driver, authentication model, and UUID or ULID usage match the package assumptions. Run a sandbox install on your target Laravel version rather than relying on the release notes.
- How does tomato-user-activities capture user activity from requests?
- The package is described as an advanced logger that saves user activities from requests, but the exact capture mechanism is not detailed in the provided context. Expect application-level instrumentation or middleware-style logging, and verify which actions are covered by default. Define your event taxonomy and test for missing or duplicate events before production use.
- Do I need to publish config and migrations for tomato-user-activities?
- Laravel packages of this type typically provide publishable configuration and migrations, and the evaluation expects that integration pattern. Publish them in a sandbox, inspect the activity table schema, indexes, and retention-related fields, then run migrations in staging. Treat schema ownership as an explicit decision because activity tables can grow quickly.
- Can tomato-user-activities support multi-tenant Laravel applications?
- Multi-tenancy support is not confirmed in the provided context, so inspect the schema and scoping logic before assuming it works for tenant isolation. You need to verify whether activities are scoped by tenant, user, guard, or request context. If scoping is missing, plan application-level instrumentation and access controls to prevent cross-tenant data exposure.
- Does tomato-user-activities support queues, pruning, export, and permissions?
- The evaluation flags queues, pruning, export, and permissions as key questions rather than confirmed features, so validate each against the code and documentation. Activity tables grow quickly, so plan for async or queued writes, indexes, pruning or partitioning, and archival. Also define who can view audit data and how exports are authorized.
- How does tomato-user-activities integrate with TomatoPHP and Filament admin panels?
- The package is positioned for TomatoPHP applications and is expected to integrate with TomatoPHP admin panels and Filament-based systems for activity feeds. Non-TomatoPHP Laravel apps should run a compatibility spike first. Verify Filament and TomatoPHP dependency versions, panel registration, and whether the feed is read-only or supports filtering and drill-down.
- What changed in tomato-user-activities v1.0.3 and is it a breaking release?
- The v1.0.3 release notes contain only a Full Changelog link and disclose no breaking changes, features, deprecations, migration steps, or security notes. Treat it as a low-signal patch release, but inspect the v1.0.2 to v1.0.3 diff before upgrading. Do not certify the upgrade as safe from the release metadata alone.
- What are the production risks of using tomato-user-activities for audit trails?
- Main risks include unverified Laravel and PHP compatibility, schema and migration ownership, PII and retention handling, incomplete event coverage, and write amplification as activity volume grows. Plan indexes, queued writes, pruning or partitioning, archival, and query limits for admin views. Review privacy rules and audit-data access before promoting to production.
- Is tomato-user-activities actively maintained and tested, and what alternatives should I consider?
- The provided context does not include test coverage metrics or maintainer responsiveness, so validate issue activity, release cadence, and CI results before committing. Community package support should be confirmed through real issue response and upgrade history. Compare with established Laravel activity-log packages and an in-house audit table if coverage or maintenance signals are insufficient.
Weaver
How can I help you explore Laravel packages today?