Weave Code
Infy Tracker Laravel Package
infyomlabs/infy-tracker
InfyTracker is a Laravel package that captures application exceptions and errors, stores them in your database, and sends notifications via email or Slack. It includes a dashboard to review, filter, and manage tracked issues, helping teams monitor production errors without relying on external servic...
Simple Task and Time Management tool for small teams
Frequently asked questions about Infy Tracker
- How do I install InfyTracker in a Laravel application?
- Install the package with Composer using composer require infyomlabs/infy-tracker, then follow the README for publishing assets, configuration, and running migrations. Because v1.0.0 adds schema changes, run migrations in a staging environment first. Confirm the package's service provider and asset build steps match your Laravel version before deploying.
- Which Laravel and PHP versions does infyomlabs/infy-tracker support?
- The package is built for standard Laravel applications, but the exact PHP and Laravel constraints are defined in its composer.json and README. Check those constraints before installing, especially if you are on an older Laravel LTS or a newer major release. The v1.0.0 release notes do not list new framework requirements, so existing supported versions likely remain valid.
- Does v1.0.0 require a database migration for the time entry project column?
- Yes, adding project context to time entries is a schema change, so plan a migration as part of the upgrade. The release assessment flags an open question about whether the new column is nullable and how historical rows are backfilled. Test the migration against a restored production snapshot and verify that older time entries render correctly after the change.
- How does the new permission scoping affect which projects and users are visible?
- Users will only see projects and user lists they have permission to manage, which is a silent data-visibility change from earlier behavior. The exact gate lives in the package's policies, and whether you can configure it per role depends on how your app maps roles to those gates. Expect some stakeholders to perceive the narrower lists as a regression, so communicate the change before rollout.
- Can admins edit other users' time entries, and is there an audit log?
- The v1.0.0 changes expand write scope so admins can add or update any user's time entry. The assessment does not mention a built-in audit trail for those edits, which is a control gap if you use time data for billing or utilization. If you need accountability, add logging around the package's time entry actions or verify whether the package exposes events you can hook into.
- Why was the one-minute time entry validation removed, and what should I watch for?
- Removing the one-minute rule lowers the guardrail on entry granularity and can increase sub-minute and duplicate time entries. Those entries can propagate into reporting and billing accuracy, so monitor reports after upgrading. The assessment does not specify whether the change applies to manual entry, the live timer, or both, so test both paths in staging.
- Is the new time entry date filter timezone-aware and inclusive at boundaries?
- Timezone awareness and boundary inclusivity are listed as open questions for the new time entry date filter. Test the filter in your application's configured timezone and check entries exactly at the start and end of the selected date range. If your team works across timezones, document the expected behavior before relying on the filter for reporting.
- Does JPEG attachment support introduce upload security risks?
- JPEG support broadens the accepted upload surface, so confirm that MIME validation and file-size limits are enforced. The release assessment flags this as a risk to verify rather than assuming the package already hardens uploads. Add or extend validation tests for disallowed file types and oversized files before exposing the feature to users.
- How should I test the v1.0.0 upgrade in a Laravel app?
- Add targeted tests for permission-scoped project and user listings, the new project column on historical time entries, date filter boundaries, and JPEG attachment validation. Exercise the five changed user-facing surfaces: task listing, time entry listing, project dropdown, user dropdown, and attachments. Run those tests against a staging clone with production-like data so you catch visibility and reporting regressions.
- What is the safest production migration path for InfyTracker v1.0.0?
- Treat v1.0.0 as a controlled major bump even though the label is a minor-style release: pin your current version, branch, and install the upgrade in a staging clone of production data. Run migrations against a restored snapshot, then diff pre- and post-upgrade behavior on task listing, time entry listing, project and user dropdowns, and attachments. Roll out with a rollback plan and watch for silent data-visibility changes from the new permission scoping.
Weaver
How can I help you explore Laravel packages today?