- What is ayvazyan10/nova-imagic and what does it do?
- Nova Imagic is a Laravel Nova image field package for uploading and manipulating images directly inside the Nova admin panel. It provides an editing interface and flexible field configuration so developers can crop, adjust, organize, and reuse images without a separate media tool. In version 2.0 it also owns a media catalog, private storage writes, and authenticated owner-scoped routes for previews.
- How do I install nova-imagic in a Laravel Nova application?
- Installation is a Composer require followed by php artisan migrate. The migration is additive because it creates a new media catalog table, so it is generally low risk to run. You should still confirm your Nova license, PHP and Laravel versions, and configured storage disk before installing.
- Which Laravel, Nova, and PHP versions does Imagic 2.0 support?
- Imagic 2.0 targets PHP 8.2 or newer, Laravel 12, Nova 5, and Intervention Image 3.11 or newer. PHP 8.1 with Laravel 9 through 11 and Nova 4 are described as EOL migration-only combinations, not recommended fresh installs. If your app is on Laravel 10 or 11 or Nova 4, treat adoption as a stack upgrade project rather than a drop-in field install.
- Does nova-imagic support S3 storage or only local disks?
- The package works with Laravel Storage, so it can use a configured local disk or an S3 disk as long as the required Flysystem S3 adapter is present. Its media UUID indirection keeps stored field values decoupled from disk paths, which helps with local to S3 migration. You should still plan lifecycle and retention rules for originals and thumbnails.
- Why are nova-imagic images private by default and how are they served?
- Version 2.0 stores images privately and resolves media references server-side through authenticated owner-scoped routes. Private storage paths are not exposed to the browser, and fields hold an opaque media reference rather than a public URL. If your application assumes public image URLs, review delivery carefully because missing access can appear as a 403 or missing image rather than an exception.
- Can I import existing image URLs or file paths into the Imagic media catalog?
- There is no automated import into the media catalog. Legacy URL, path, and JSON values remain readable, but they are not migrated, so old images will not automatically get owner scoping, thumbnails, or library entries. Backfilling legacy media is custom work, and you should decide whether catalog coverage is required or can be sunset.
- Do I need Intervention Image 3 to use nova-imagic?
- Imagic 2.0 expects Intervention Image 3.11 or newer. That matters if you have custom transforms or existing image-processing code built against an older Intervention API, because some of it may need rework. Intervention Image 2.7 may be a transition path, but it is not the target for Imagic 2.0.
- Is nova-imagic safe to use in production?
- The package is mechanically easy to install, but production adoption carries real risks. The main concerns are vendor concentration around a small single-maintainer package tightly coupled to commercial Nova and current Laravel versions, plus the behavior change from private-by-default image delivery. You also gain new stateful surfaces, including a media table, routes, and storage objects, that need backup, monitoring, and security review.
- Can I roll back nova-imagic 2.0 after installing it?
- The install migration is additive, which reduces immediate risk, but you should verify the rollback path for the specific release before deploying. Pre-existing field values are preserved and remain readable rather than rewritten by the catalog. Take backups and test rollback in staging because the package also introduces storage objects and routes beyond the database table.
- What license and support model does nova-imagic use, and what are the alternatives?
- Check the package repository and Composer metadata for the package license because it is separate from your commercial Nova license. Support and release cadence are important to confirm, especially if you need an SLA path rather than community-only maintenance. Alternatives include Nova's built-in image fields or URL-in-column patterns, but those do not provide the same private media catalog and owner-scoped resolution.