- What is zipavlin/redline used for in a Laravel application?
- Redline is a Laravel package by zipavlin for localized, on-site visual bug reporting. It provides a widget, dashboard, and API so authenticated host users can submit and review reports. Reports can include members, priority, and due dates, and the package stores data in a dedicated SQLite connection.
- How do I install and configure Redline in Laravel?
- Require the package with Composer, publish its config and assets, then configure the LaravelAuthProvider and LaravelGuardProvider so Redline can resolve host users. Set a writable SQLite database path with correct permissions, run migrations, and verify the widget and dashboard are injected for authenticated users. The release notes do not document supported Laravel and PHP versions, so check composer.json and the README before installing.
- Does Redline work with Laravel session authentication instead of a separate login?
- Yes. Version 0.2.0 adds LaravelAuthProvider and LaravelGuardProvider so session-authenticated host users can use the widget and dashboard without a separate Redline login. It fits a Laravel monolith or app with session auth and a clear role model. API-only or token-auth SPA stacks need explicit validation of cookie and CSRF behavior for media.
- What database does Redline use, and can I use MySQL or PostgreSQL instead?
- Redline uses a dedicated SQLite connection as its single backend. That is a scaling and high-availability constraint and adds a second persistence technology even if your host uses MySQL or PostgreSQL. You need a persistent writable volume, backups, monitoring, and validation for multi-node deployments because SQLite on shared storage can cause contention or corruption risk.
- Is zipavlin/redline production-ready?
- Treat it as pre-1.0 software: it is feasible for a Laravel host but not drop-in, and contract v2 includes breaking wire changes. Production use requires role mapping, SQLite operations, upgrade policy, and media/CSRF validation. The release notes do not establish a support or licensing model, so confirm those before relying on it.
- What breaking changes are in Redline contract v2?
- Contract v2 removes the has_media report filter, removes user_agent from report payloads, removes the Orbit/FileStorageProvider backend, and removes JWT-in-media URLs. Email PII now returns 422 for non-developer/admin roles, and the origin gate applies to all login modes. Existing frontend filters, media links, and cached HTML that depend on v1 behavior need migration and invalidation.
- How do report members and assignment work in Redline?
- The author is never a member, and assigning the author is a no-op rather than a 422. Any member can remove themselves, and claiming a report auto-assigns the acting user when eligible. These semantics are specific, so align product and UX flows before depending on member-based workflows.
- How should I map host roles to Redline developer or admin for email PII?
- Redline implies guest, pending, approved, developer, and admin roles, and only developer/admin roles can access email PII; other roles receive a 422. You must define which host roles map to Redline developer and admin and audit who can legitimately see email PII. Broader GET /user access for authenticated users and role mapping correctness remain security review items.
- How do I upgrade Redline safely in production?
- Use the redline:update command to run package updates in a controlled way, and decide explicitly whether production will allow the Composer post-package-update hook to run migrations. Test contract v2 changes in staging, invalidate cached HTML and old media links, and document a runbook. Back up the SQLite database before upgrading.
- Does Redline support multi-tenancy or per-team isolation?
- The provided release notes do not establish multi-tenancy, per-project scoping, or per-team isolation boundaries. If you need those, validate them explicitly or treat Redline as a single-application bug reporting tool. The dedicated SQLite backend and member model do not by themselves guarantee tenant isolation.