Weave Code
Avatar Laravel Package
orchestra/avatar
Orchestra Avatar is a Laravel package for managing user profile avatars. It provides a simple API to upload, store, and render avatars, with fallbacks for users without a custom image, making it easy to add consistent avatar handling to any Laravel application.
Avatar Component for Orchestra Platform
Frequently asked questions about Avatar
- What is orchestra/avatar used for in a Laravel application?
- Orchestra Avatar is a single-responsibility Laravel package for managing profile avatars on Eloquent models. It lets you attach, replace, and remove an image, generate size-parameterized URLs, use Blade helpers, and fall back to Gravatar or a configured placeholder. It fits apps that need consistent avatar handling without building upload, storage, and fallback logic from scratch.
- How do I install orchestra/avatar in Laravel?
- Install it with Composer using composer require orchestra/avatar, then register or auto-discover the service provider and optionally publish its config. You then configure a storage disk and directory and add the avatar relation or accessor to your user model. The context does not imply migrations, queue workers, or external services beyond the optional Gravatar fallback, but check composer.json constraints first.
- Which Laravel versions does orchestra/avatar support?
- The latest release identified is v6.0.0, which targets Laravel 8, and the context shows no declared support for Laravel 9 through 12. On Laravel 9 or newer, the package likely cannot be installed without a framework downgrade or a fork. Confirm the composer.json illuminate/* and PHP constraints before adopting it.
- Does orchestra/avatar work with any Eloquent model or only Orchestra Platform users?
- The README claims it works with any Eloquent model, but the TPM assessment flags that as unverified because the package ships under the Orchestra Platform umbrella. It may assume Orchestra-specific user contracts, auth guard behavior, or view namespaces. Test it against a plain Laravel User model before committing.
- How do I configure avatar storage and fallbacks?
- Configuration is described as storage-disk and directory driven, with Flysystem underneath and a choice between Gravatar or a configured placeholder fallback. That lets you move from local disk to object storage or a CDN per environment without rewriting application code. Publish and review the config to confirm exact keys for disk, directory, placeholder, and Gravatar behavior.
- Does orchestra/avatar resize images or just generate size-based URLs?
- The overview mentions size-parameterized URLs but does not document whether resizing happens in-package via GD/Imagick or is delegated elsewhere. It also does not clearly state whether generated sizes are fully under your control or bound to the helper API. Verify this before relying on multiple avatar dimensions.
- Is orchestra/avatar safe for production image uploads?
- Image upload is security-sensitive, and the package description does not claim built-in validation, so assume you own MIME and extension checks, file size limits, SVG or polyglot rejection, and decompression-bomb protection. Serve avatars from a controlled disk or CDN rather than an executable web-served directory. Also plan cleanup for orphaned files on replace and delete unless retention behavior is documented.
- How does the Gravatar fallback affect privacy?
- The Gravatar fallback sends an md5 hash of the user's email to a third-party endpoint when rendered, according to the assessment. That creates privacy and compliance questions for EU users and adds an external availability dependency. The overview mentions a configured placeholder, but it does not document a per-environment switch to disable Gravatar, so confirm that before production.
- How can I test avatar upload and deletion in Laravel?
- The context does not describe a dedicated testing helper, so test the integration through your own Laravel feature tests. Use Storage::fake to assert upload, replace, and delete behavior, and assert URL and fallback output for users without a custom image. Include validation and cleanup cases because those responsibilities likely sit in your application.
- Is orchestra/avatar actively maintained, and what alternatives exist?
- Maintenance signals are weak: v6.0.0 targets Laravel 8, there are no listed dependents or stars, and the major bump has a single-line changelog with no upgrade guide. Treat it as unproven and verify maintainer ownership and support commitments. If you need Laravel 9+ support, consider a maintained Gravatar/avatar package, spatie/laravel-medialibrary for broader media handling, or a small custom accessor plus Intervention Image.
Weaver
How can I help you explore Laravel packages today?