- What is jstoone/nova-mailman used for?
- Nova Mailman adds a database-backed email management panel to Laravel Nova so you can create and edit mailables, customize subjects and HTML or Markdown bodies, preview rendered emails, and send test messages without code changes. It is aimed at developer, QA, and support workflows where teams need visibility into generated mail. Release 1.2.0 also adds in-tool mail removal, so it should be treated as an administrative surface rather than a passive viewer.
- How do I install nova-mailman in a Laravel application?
- Install the package with Composer, then publish any provided configuration and frontend assets and run migrations if the package ships them. Because the tool registers server-side routes and a Vue/SCSS frontend, confirm the service provider and route registration load correctly and that published assets resolve. Check the package documentation for the exact publish tags and any required Nova setup.
- Which Laravel, PHP, and Nova versions does nova-mailman support?
- The README excerpt does not list version constraints, so check the package composer.json and release notes before installing. Since it is a Laravel Nova tool, the Nova major version matters as much as the Laravel and PHP versions. Pin a version that matches your application Laravel, PHP, and Nova stack and test in a sandbox first.
- Can nova-mailman be used safely in production?
- It is best treated as a developer, QA, and support debugging tool, and production use should be gated behind strict access control and a retention policy. Release 1.2.0 adds a destroy route and in-tool mail removal, which turns it into a destructive administrative surface. Avoid exposing it on internet-accessible environments and restrict it to trusted operators or non-production systems unless you have reviewed authorization and deletion behavior.
- What does the remove mails feature in 1.2.0 actually delete?
- Version 1.2.0 introduces a destroy route and in-tool mail removal, but the available context does not clarify whether it deletes mail from the underlying mail storage, the package own records, or only the Nova UI listing. Confirm the semantics in the package source or documentation before enabling it anywhere important. Until then, assume deletion is permanent and test only against disposable mail data.
- How should I secure the nova-mailman destroy route?
- Put the tool behind Nova authentication middleware and an explicit gate or policy that limits who can view and delete mail. Keep CSRF protection enabled, add environment gating so the route is unavailable outside approved environments, and log deletions for auditability. If you cannot confirm the route authorization behavior from the package, wrap or restrict it at the application level.
- Do I need to rebuild or republish assets after upgrading nova-mailman?
- Yes, plan to republish or rebuild frontend assets after upgrading, especially to 1.2.0. That release splits Vue components, which may break local overrides, and includes an SCSS compile fix that should reduce install-time 500 errors. Verify published assets and view paths after the upgrade, and confirm whether the package uses Vite, Mix, or precompiled files.
- How do I upgrade nova-mailman to version 1.2.0?
- Pin the new version, update Composer dependencies, republish any package configuration and assets, rebuild frontend assets, and recheck route registration for collisions. Treat it as a minor upgrade with one material behavioral addition: mail deletion. Test deletion only against disposable data, document the behavior, and promote through local or sandbox and shared staging before production.
- How can I test nova-mailman, including the new delete route?
- Use a local or sandbox environment with disposable mail data and exercise the create, edit, preview, send-test, and delete flows end to end. Add feature tests that assert unauthenticated and unauthorized users cannot reach the destroy route, and that authorized deletion behaves as expected. Also check for route-name or path collisions and confirm the 1.2.0 timestamp format change does not break screenshots or assertions.
- What are the alternatives to nova-mailman for debugging Laravel mail?
- Common alternatives include Mailpit or MailHog for local SMTP capture, Mailtrap for hosted inbox testing, and Laravel Telescope or log-based inspection for generated messages. Nova Mailman differentiator is database-backed template management inside Laravel Nova, with previews and test sends from the same interface. If you only need to capture outgoing mail for debugging, a local mail catcher may be simpler and lower risk.