Weave Code
Nova Field Cloudinary Laravel Package
silvanite/nova-field-cloudinary
A Laravel Nova field that stores and serves images through Cloudinary, giving your admin panels powerful upload, transformation, and delivery options without writing custom integration code.
A Laravel Nova Image Field with Flysystem Adapter for storing and retrieving media from Cloudinary
Frequently asked questions about Nova Field Cloudinary
- How do I install silvanite/nova-field-cloudinary in a Laravel Nova application?
- Install the package with Composer, publish its config, add Cloudinary credentials to your environment, and replace standard Nova image or file fields with the Cloudinary-backed field on selected resources. Because the last release was in 2019, run the install on a throwaway branch against your actual PHP, Laravel, and Nova versions before touching production. Keep the first pilot limited to one low-risk model.
- Does silvanite/nova-field-cloudinary support Laravel Nova 4 or Nova 5?
- There is no verified compatibility with Nova 4 or Nova 5 in the available context. The last release was 2019-11-19, which predates those Nova generations, and no modern PHP, Laravel, Nova, or Cloudinary SDK compatibility is documented. Treat Nova 4 and Nova 5 support as unproven and run a time-boxed compatibility spike. If it fails, fork the field and config classes or reimplement the thin pattern in-house.
- How does the Cloudinary field store image references on an Eloquent model?
- The field persists a Cloudinary public ID or URL on the model and resolves delivery and transformation URLs at render time. Your database therefore stores the reference rather than the binary, and Cloudinary handles delivery. It fits back-office admin surfaces without moving your application's own filesystem to Cloudinary. Plan asset ownership upfront so the field only deletes what it uploaded.
- Does deleting an image in Laravel Nova also delete it from Cloudinary?
- The v1.3.0 release fixed Audio and File deletion so remote assets are actually destroyed, which is a behavioral contract change rather than a cosmetic patch. Before upgrading, confirm whether remote delete fires on field clear, model delete, cascading delete, and bulk actions, and whether it is idempotent. Test against disposable assets and confirm Cloudinary backup or retention can recover a misfired delete. Destructive delete semantics are a major production risk.
- Can I use this Nova field for Cloudinary video, audio, and raw files as well as images?
- v1.3.0 broadens the field to mixed media with CloudinaryVideo and better raw and video support, while also reducing Nova thumbnail size for faster index views. Adopt per asset type: prove images and files first, then add audio, video, and raw once deletion and transformation behavior is verified. Keep an inventory of which resources use which asset types. Transformation and video quota costs should be reviewed before broad rollout.
- What PHP, Laravel, Nova, and Cloudinary SDK versions does this package support?
- The available assessment does not confirm supported PHP, Laravel, Nova, or Cloudinary SDK versions. The package has not had a release since 2019-11-19 and has no verified compatibility with modern stacks. Pin the versions you actually test and validate them against your current and next upgrade cycles. If the matrix does not match, fork or reimplement rather than absorbing open-ended breakage.
- Is silvanite/nova-field-cloudinary maintained and safe for production use?
- Maintenance risk is high: the last release was 2019-11-19, the repository has about 27 stars and zero dependents, and there is no verified compatibility with modern PHP, Laravel, Nova, or Cloudinary SDK behavior. Code risk is lower than maintenance risk because the package is a thin field set plus Flysystem adapter. Frame it internally as a useful pattern but a stale artifact, and force an explicit adopt, pin, fork, or reimplement decision. Do not put a critical admin media path on it without a named owner.
- How should I configure Cloudinary credentials for this Laravel Nova field?
- Publish the package config, supply Cloudinary credentials through environment variables, and scope them per environment or tenant so staging pilots never touch production assets. Account for config:cache drift and define a rotation process before go-live. Avoid committing secrets, and use a dedicated staging Cloudinary cloud for compatibility spikes. Review whether you need upload presets, folders, or private and signed delivery.
- Can I mix Cloudinary with local or S3 disks on the same Eloquent model?
- The assessment advises against mixing local or S3 disks with Cloudinary on the same model because deletion semantics diverge and orphans become invisible. Keep field-owned Cloudinary assets separate from shared or evergreen assets, which should use plain public-ID columns with lifecycle handled by jobs or observers. Define ownership up front so the field deletes only what it uploaded. This keeps the blast radius small during a pilot.
- How do I test Cloudinary uploads, transformations, and deletes in CI for this field?
- Use a dedicated staging Cloudinary cloud and exercise replace, clear, delete, and bulk actions against disposable assets. The available context does not confirm that image, video, audio, file, and raw upload, transform, and destroy paths are covered by tests you can run in CI, so verify coverage before relying on it. Add tests for idempotent delete and for Nova index thumbnail behavior. Keep legacy identifiers until URL parity is verified.
Weaver
How can I help you explore Laravel packages today?